Ometria’s integration with Yotpo Loyalty & Referrals means that your Yotpo loyalty and referrals data can be stored against your Ometria contact’s records.
See also: Yotpo's guide for launching an on-site Loyalty & Referrals programme.
The integration works by automatically importing the live contact data into Ometria, where you can use the data to personalise your campaigns and uncover new insights to inform your marketing strategy.
Multi-store Yotpo reviews
If you have more than one store with Yotpo reviews and want all of that data in your Ometria account, you'll need to set up a separate connection for each store.
Before you begin
To get started with Yotpo, contact your Customer Success Representative.
Next, set up a Yotpo Loyalty & Referral account.
Setting up your integration with Yotpo Loyalty & Referrals
On Yotpo navigate to the General settings to view both your App key and Secret Key (you will need to be administrator to access these details):
While on Yotpo, open another tab and navigate to Yotpo loyalty and access General settings to view your API key and GUID details:
In Ometria, go to Settings and select the Connections tab:
Click Add new connection, then select Yotpo loyalty & referrals.
This will load the connection details required for completion
| Field | Description |
| Name | Enter any name for the Yotpo connection |
| App key | This is located in your Yotpo account in the General settings (earlier step) |
| Secret key | This is located in your Yotpo account in the General settings (earlier step) |
| API key | This is located in your Yotpo Loyalty > General settings (earlier step) |
| GUID | This is located in your Yotpo Loyalty > General settings (earlier step) |
| Standard vs. Custom field options | By default, the integration will push all field values from Yotpo to custom fields on the customer profile in Ometria. For the fields listed below, you can choose to use the standard Ometria fields instead. To use the standard field instead of the custom field, tick the box for the relevant field(s) below. |
| Loyalty opt-in identifier | See section below |
Loyalty opt-in identifier
In the final step of the integration configuration flow, you'll be asked to select which property Ometria should use as the loyalty opt-in identifier:
This depends on whether you're using Yotpo's Legacy accounts or the newer Customer accounts:
-
Legacy accounts use
has_store_account, stored in Ometria asyotpo_has_platform_account. -
Customer accounts use
is_opt_in, stored in Ometria asyotpo_is_opt_in.
If you are migrating from Legacy to Customer accounts, you'll need to enable Customer accounts in Yotpo first, which makes the is_opt_in property available.
Then update the setting in Ometria so the integration uses is_opt_in as the loyalty identifier.
These changes should be made at around the same time in both platforms to ensure data consistency and avoid gaps in tracking opt-in status.
For more context on Yotpo's Customer Accounts and loyalty opt-ins, see Yotpo's documentation on using Loyalty & Referrals with Shopify's new Customer Accounts.
Final steps
Select Create.
Your Yotpo Loyalty & Referrals connection is set up.
Next you'll need to raise a request with the Support team to get your custom events set up. After that, Ometria's Creative team will need to add the triggers to your email templates.
Data passed to Ometria
Ometria retrieves two types of data from Yotpo Loyalty & Referrals:
- Custom fields - fields you create manually in Ometria.
- Default fields - fields that already exist in Ometria's database.
Yotpo also sends Ometria custom events.
Create your custom fields
Once your Yotpo Loyalty & Reviews connection is set up in Ometria, you'll need to create the custom fields below for retrieving the data.
You only need to create the fields that you think will provide value to your marketing strategy.
Follow the steps in Create a custom field to set up the following:
| Ometria Field ID | Description | Type | Yotpo field |
yotpo_perks_redeemed |
The number of perks/rewards the customer has redeemed. E.g. |
Number | perks_redeemed |
yotpo_points_earned |
Total points the customer has earned in their lifetime. E.g. |
Number | points_earned |
yotpo_points_balance |
Current points balance (after point redemptions, expirations etc.) E.g. |
Number | points_balance |
yotpo_points_expire_at |
Next expiry date for a batch of points. E.g.
Note: Not all Yotpo accounts use this field, please check with your Yotpo representative.
|
Date | points_expire_at |
yotpo_next_points_expire_on |
Next expiry date for a batch of points. E.g.
Note: Not all Yotpo accounts use this field, please check with your Yotpo representative.
|
Date | next_points_expire_on |
yotpo_next_points_expire_amount |
The amount of points that will expire on the next expiration date.
Note: Not all Yotpo accounts use this field, please confirm with your Yotpo representative.
|
Number | next_points_expire_amount |
yotpo_loyalty_enrolled |
Whether or not the customer is enrolled in the loyalty program. E.g. |
String (True/False) | opt_in |
yotpo_loyalty_enrolled_date |
The date the customer enrolled in the loyalty program. E.g. |
Date | opted_in_at |
yotpo_has_store_account |
Whether or not the customer has a POS account. E.g. |
String (True/False) | has_store_account |
yotpo_tier |
The contact's current tier name. E.g. |
String | vip_tier_name |
yotpo_tier_entry_date |
Date the customer entered their current tier. E.g. |
Date | vip_tier_entry_date |
yotpo_tier_expiration_date |
The expiration date of the current tier if maintenance goals aren’t reached. E.g. |
Date | vip_tier_expiration |
yotpo_maintain_tier_points |
Points needed to maintain tier. E.g. |
Number | vip_tier_maintenance_requirements.points_needed |
yotpo_maintain_tier_amount |
Spending amount needed to maintain tier (in cents). E.g. |
Number | vip_tier_maintenance_requirements.amount_cents_needed |
yotpo_maintain_tier_purchases |
Purchases needed to maintain tier. E.g. |
Number | vip_tier_maintenance_requirements.purchases_needed |
yotpo_maintain_tier_referrals |
Referrals needed to maintain tier. E.g. |
Number | vip_tier_maintenance_requirements.referrals_needed |
yotpo_upgrade_tier_points |
Points needed to upgrade tier. E.g. |
Number | vip_tier_upgrade_requirements.points_needed |
yotpo_upgrade_tier_amount |
Spending amount needed to upgrade tier (in cents). E.g. |
Number | vip_tier_upgrade_requirements.amount_cents_needed |
yotpo_upgrade_tier_purchases |
Purchases needed to upgrade tier. E.g. |
Number | vip_tier_upgrade_requirements.purchases_needed |
yotpo_upgrade_tier_referrals |
Referrals needed to upgrade tier. E.g. |
Number | vip_tier_upgrade_requirements.referrals_needed |
yotpo_firstname |
If you have not specified that you want to use the standard first name field, this will be used. E.g. |
String | first_name |
yotpo_lastname |
If you haven't specified that you want to use the standard last name field, this will be used. E.g. |
String | last_name |
date_of_birth |
If you haven't specified that you want to use the standard date of birth field, this will be used. E.g. |
Date |
|
Migrating from legacy to customer accounts
If you are migrating from legacy to customer accounts, be aware of the following behaviour:
- The
yotpo_is_opt_inproperty is used as the loyalty opt-in identifier for new customers after the switch. - Existing customer data remains unchanged — only
yotpo_has_platform_accountmay be present for customers acquired before the migration.
Updating your campaign logic
When migrating, you'll need to update any automated campaign conditions that reference the legacy opt-in property to ensure compatibility with both old and new customer data.
yotpo_has_platform_account. If you are using a different property, substitute it accordingly. Check with your Customer Success Representative if you're unsure.Previous condition:
yotpo_has_platform_account = trueUpdated condition:
(
yotpo_has_platform_account = true
AND yotpo_is_opt_in is not known
)
OR
yotpo_is_opt_in = trueThis ensures your campaigns continue to capture both customers acquired before the migration and those who opted in under the new Customer accounts setup.
Event triggers
Full list of the Yotpo event triggers Ometria supports: Yotpo Loyalty & Referrals: Supported events
Use cases
Automation campaigns
Points reminder
Set up a campaign to remind your customers how many loyalty points they have available using the entry trigger:
- The contact has entered or exited a segment
- The contact had entered a segment - which is - Accumulator Point Reminder.
Points confirmation
Set up a campaign to let your customers know how many loyalty points they have after placing an order by using the entry trigger:
- Custom date - Last purchase date - Is today
New tier confirmation
Set up a campaign to let your customers know when they have moved into a new loyalty tier by using the entry trigger:
- Contact entered or exited a segment
- Contact has entered a segment - which is - [select your loyalty tier]
Loyalty welcome
Set up a campaign to thank your customers for opting into your loyalty programme by using the entry trigger:
- Custom date - [Opt-in date field name] - Is today
Broadcast campaigns - dynamic blocks
Configure your broadcast campaign templates to display only for contacts in your loyalty tier segments and tailor the information specifically to them:
Using merge tags to convert cents into dollars
Yotpo sends currency values to Ometria as cents, not dollar amounts (e.g. 4999 instead of 49.99).
You can use merge tags to convert these values into dollar amounts in your marketing messages:
| Field | Merge tag |
yotpo_maintain_tier_amount |
{{ ("%.2f" % ((properties.yotpo_maintain_tier_amount | int) /100) }} |
yotpo_upgrade_tier_amount |
{{ ("%.2f" % ((properties.yotpo_upgrade_tier_amount | int) /100) }} |
Comments
0 comments
Please sign in to leave a comment.