Configure destinations for SevenRooms

SevenRooms is a guest experience and data platform for the hospitality industry. Restaurants, hotels, and other operators use it to manage guest profiles, reservations, and transactions.

Use Amperity to activate an audience into SevenRooms. Build a query or segment that includes the email field, and then send it to SevenRooms.

SevenRooms builds its guest segments from client tags, so Amperity activates an audience as a named client tag applied to matching guest profiles. Amperity matches guest profiles by email, applies the tag to members of the audience, and removes the tag from guest profiles that leave the audience. Amperity also writes profile attributes – such as phone number, first name, and last name – onto the matching guest profiles. Each run sends only the additions, removals, and attribute changes since the previous run, not the full audience.

A SevenRooms client tag is addressed as group:tag. The Tag group is set once per destination and the Tag name identifies the audience; together they form the tag that Amperity applies. Changing either one sends the entire audience again under the new tag.

Note

This destination uses the SevenRooms API .

Beta

The SevenRooms connector is currently in beta. Contact your Amperity representative to learn more.

Note

SevenRooms must already contain a guest profile that matches an audience member’s email within the venue group. Amperity applies tags and writes attributes to guest profiles that already exist; an audience member that SevenRooms cannot match is reported as a failed row.

Caution

A run can partially succeed. Individual audience members that SevenRooms rejects – for example, a member with no matching guest profile or a field value that is not valid for a guest profile – are counted as failed rows while the rest of the run completes.

Note

Amperity sends one request per audience member, at a conservative rate of approximately 10 requests per second. This rate is an Amperity-side limit, not a published SevenRooms API limit.

Get details

Review the following details before configuring credentials for SevenRooms and before configuring Amperity to send audiences to SevenRooms.

	Credential settings Client ID and Client Secret Required The Client ID for your SevenRooms API credential. The Client Secret for your SevenRooms API credential. Tip Request API credentials (a client ID and client secret) from SevenRooms. API access must be provisioned for your account before Amperity can connect to SevenRooms.
	Required configuration settings Base URL Required The base URL for the SevenRooms API, including the version path. For example: https://demo.sevenrooms.com/api-ext/2_2. Your production base URL differs from the demo URL. Venue Group ID Required The venue group ID for your SevenRooms account. This scopes the guest profiles that Amperity tags to a single venue group. Tag group Required The SevenRooms client tag group that the audience tag belongs to. SevenRooms addresses a client tag as group:tag; this setting is the group portion and is the same for every audience sent to this destination. Audience primary key Required The primary key for the audience. Set to “email”. Tag name The SevenRooms client tag that Amperity applies to audience members. This is the tag portion of the group:tag value and identifies the audience within SevenRooms. Changing the tag name or the tag group sends the entire audience again under the new tag.
	A query or segment that outputs the email field and any profile attributes to send to the SevenRooms audience.

Configure credentials

Configure credentials for SevenRooms before adding a destination.

An individual with access to SevenRooms should use SnapPass to securely share “Client ID and Client Secret” details with the individual who configures Amperity.

To configure credentials for SevenRooms

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select SevenRooms. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential vary by credential type. For the “sevenrooms” credential type, configure settings, and then click Save. Client ID and Client Secret Required The Client ID for your SevenRooms API credential. The Client Secret for your SevenRooms API credential.

Add destination

Use a sandbox to configure a destination for SevenRooms. Before promoting your changes, send a sample audience, and then verify the results in SevenRooms. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for SevenRooms

	Open the Destinations page, select the New destinations button, and then select Orchestration. To configure a destination for SevenRooms, do one of the following: Click the row in which SevenRooms is located. Destinations list alphabetically and you can scroll up and down the list. Search for SevenRooms. Start typing “Seven”. The list filters to show only matching destinations. Select “SevenRooms”.
	Select the credential for SevenRooms from the Credential dropdown, and then click Continue. Tip Amperity validates the connection when the destination is saved. If the connection cannot be validated, an error is shown and the destination is not saved.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Base URL Required The base URL for the SevenRooms API, including the version path. For example: https://demo.sevenrooms.com/api-ext/2_2. Your production base URL differs from the demo URL. Venue Group ID Required The venue group ID for your SevenRooms account. This scopes the guest profiles that Amperity tags to a single venue group. Tag group Required The SevenRooms client tag group that the audience tag belongs to. SevenRooms addresses a client tag as group:tag; this setting is the group portion and is the same for every audience sent to this destination. Audience primary key The primary key for the audience. Set to “email”. Tag name (Required at orchestration) The SevenRooms client tag that Amperity applies to audience members. This is the tag portion of the group:tag value and identifies the audience within SevenRooms. Changing the tag name or the tag group sends the entire audience again under the new tag.
	After configuring this destination users may use: Orchestrations to send query results Orchestrations and campaigns to send audiences Orchestrations and campaigns to send events
	Validate the audience with SevenRooms by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by SevenRooms. Send the sample audience to SevenRooms and verify the sample audience is correct in SevenRooms. Make adjustments if necessary. Only send full audiences after validation is complete.