Zapier

Table of contents¶

• Introduction
• Getting started
• Actions
• Contact management
• Movement management
• Available webhooks
• Segment / audience triggers
• Contact triggers
• Movement triggers
• REST hooks subscription
• Use cases
• Google Ads sync
• Meta (Facebook Ads) sync

Introduction¶

The Fideltour app on Zapier lets you automate workflows without custom development. It offers two kinds of capabilities:

• Triggers: Fideltour notifies Zapier when an event occurs (contact created, audience activated, etc.). HDH acts as an intermediary, receiving the event from Fideltour and forwarding it to the Zap.
• Actions: Zapier sends data to Fideltour to create or update contacts and movements through the HDH API.

Getting started¶

To use the Fideltour app on Zapier you need:

• A Fideltour account.
• A Zapier account.
• Specific credentials to connect Fideltour from Zapier. These must be requested from hoteldatahub@fideltour.com. Along with the credentials, you'll be given the chain code and the hotel identifiers needed for contact and movement actions.

For the audience sync use cases, Fideltour's Social module must be contracted.

Actions¶

Actions let you send data from Zapier to Fideltour to create or update records.

Contact management¶

Available methods¶

Important: Fideltour treats email and identification_number as unique. If you try to create a contact with an email or document number that already exists, you'll get an error. It's recommended to check that the contact doesn't already exist (with Get contact by Email) before creating it.

Common use cases¶

Updating a contact:

1. Use Get contact by Email to get the contact's ID.

The screenshots in this guide show Zapier and Fideltour's interface in Spanish, but the fields and buttons work the same way in English.

2. Zapier returns the contact's information, including the ID.

3. Use Update contact with the ID obtained to update the data.

Parameter table — contact¶

Movement management¶

Important: a movement always belongs to a contact. To create a movement you must have the contact's Fideltour ID (obtained beforehand with the Get contact methods).

Available methods¶

Common use cases¶

Updating a movement:

1. Use Get movements list with filters (e.g. localizer + input_channel) to locate the movement.

2. Zapier returns the movement's information, including the ID.

3. Use Update movement with the ID obtained to update the data.

Parameter table — movement¶

Available webhooks¶

Triggers let Zapier react to Fideltour events in real time via REST hooks.

Segment / audience triggers¶

These triggers fire based on the audiences configured in Fideltour's Social module.

Activate Audience Segment (type 1)¶

Fires every time an audience is activated in Fideltour.

Data received in the Zap:

Deactivate Audience Segment (type 2)¶

Fires every time an audience is deactivated in Fideltour.

Data received in the Zap:

Add Contact to Audience Segment (type 3)¶

Fires every time a contact is added to the segment of an active audience in Fideltour.

Data received in the Zap:

Remove Contact from Audience Segment (type 4)¶

Fires every time a contact is removed from the segment of an active audience in Fideltour.

Data received in the Zap: identical to Add Contact to Audience Segment.

Contact triggers¶

Payloads:

• Created / updated: full contact record plus hotel_chain.
• Level change: { hotel_chain, contact, email, level, level_name, event: "level_updated" }.
• Unsubscribed: { hotel_chain, contact, email, event: "unsubscribe" }.
• Loyalty updated: Fideltour's payload plus hotel_chain and event: "loyalty_updated".
• Invalid email: Fideltour's payload plus hotel_chain and event: "email_invalid".

The permission required on the ApiUser for these triggers is contacts.

Movement triggers¶

Payload: movement data plus hotel_chain.

The permission required on the ApiUser for these triggers is movements.

REST hooks subscription¶

Zapier manages subscriptions against HDH using the customer's ApiUser:

Subscribe (when a Zap is activated):

POST https://app.hoteldatahub.io/api/v1/webhooks/zapier-webhooks-subscriptions/
Authorization: Token <jwt>
Content-Type: application/json

{
  "url": "https://hooks.zapier.com/hooks/standard/...",
  "type": 5
}

Unsubscribe (when the Zap is deactivated):

DELETE https://app.hoteldatahub.io/api/v1/webhooks/zapier-webhooks-subscriptions/{id}/
Authorization: Token <jwt>

Each ApiUser can only see and manage its own subscriptions. Required permissions by type: segments (types 1–4), contacts (types 5–10), movements (types 11–12).

For contact and movement triggers to work, Fideltour must be configured to send its webhooks to the customer's generic HDH endpoints:

Use cases¶

Google Ads sync¶

Sync audiences configured in Fideltour with Google Ads customer lists.

Additional requirements: Fideltour's Social module contracted and a Google Ads account.

1. Create a customer list in Google Ads¶

When an audience is activated in Fideltour, automatically create a customer list in Google Ads using the Activate Audience Segment trigger.

It's recommended to use the dedicated Zapier template for this.

Notes

• If a Google Ads list with the same name as the audience already exists, Zapier will return an error (Google Ads doesn't allow duplicate names).
• When activating an audience that already has contact history, Google Ads creates the list but doesn't transfer the history. See Export and import historical data.

2. Add a contact to a Google Ads list¶

When a contact is added to an active Fideltour audience, add it to the corresponding Google Ads list as well, using the Add Contact to Audience Segment trigger.

It's recommended to use the dedicated Zapier template.

Note: the Zap includes an intermediate action to find the Google Ads list by name before adding the contact.

3. Remove a contact from a Google Ads list¶

When a contact is removed from an active Fideltour audience, remove it from the Google Ads list as well, using the Remove Contact from Audience Segment trigger.

It's recommended to use the dedicated Zapier template.

Note: as with the previous case, the Zap includes an intermediate action to locate the list by name.

Export and import historical data (Google Ads)¶

When an audience already has history at the time it's first activated, transferring it one by one via Zapier is expensive. The free process is:

1. Go to the contacts section of Fideltour's CRM module.
2. Filter by the audience's segment.
3. Select all and export to Excel.
4. Within a few minutes you'll receive the export by email.
5. Adapt the Excel's structure to the format required by Google Ads.
6. Import it into the Google Ads list. There are two ways:

New customer list:

In Audience Manager, click + and select Customer list.

On the next screen, select Upload a file manually as the data source.

Give the segment a name, upload the CSV file with the contacts exported from Fideltour, and save.

Edit an existing list:

In Audience Manager, locate the corresponding list and click Edit list.

In the edit form, select Add more customers and upload the CSV file.

Meta (Facebook Ads) sync¶

Sync audiences configured in Fideltour with Facebook Business Manager audiences.

Additional requirements: Fideltour's Social module contracted and a Facebook Business Manager account.

1. Create an audience in Facebook¶

When an audience is activated in Fideltour, automatically create an audience in Facebook using the Activate Audience Segment trigger.

It's recommended to use the dedicated Zapier template.

Note: if the activated audience already has contact history, Facebook creates the audience but doesn't transfer the history. See Export and import historical data.

2. Add a contact to a Facebook audience¶

When a contact is added to an active Fideltour audience, add it to the Facebook audience as well, using the Add Contact to Audience Segment trigger.

It's recommended to use the dedicated Zapier template.

Note: unlike Google Ads, Facebook doesn't have a Zapier action to find audiences by name. This means a separate Zap is needed for each audience. If there are 3 active audiences, 3 Zaps are needed.

3. Remove a contact from a Facebook audience¶

When a contact is removed from an active Fideltour audience, remove it from the Facebook audience as well, using the Remove Contact from Audience Segment trigger.

It's recommended to use the dedicated Zapier template.

Note: same as with adding, a separate Zap is needed per audience.

Export and import historical data (Meta)¶

The process is equivalent to Google Ads, with Facebook as the final destination instead:

1. Go to the contacts section of Fideltour's CRM module.
2. Filter by the audience's segment.
3. Select all and export to Excel.
4. Within a few minutes you'll receive the export by email.
5. Adapt the Excel's structure to the format required by Facebook.
6. Import it into the Facebook audience. There are two ways:

New audience:

In Audience Manager, click Create a custom audience.

Select Customer list as the audience source.

Prepare the file following the required format. You can download the official template from this step.

Upload the CSV file with the contacts exported from Fideltour.

Edit an existing audience:

In Audience Manager, select the audience and click Actions.

Select Add customers and upload the CSV file.