See also: How does Ometria subscribe and unsubscribe contacts?
@force_optin=TRUE is an Ometria field that is passed from forms that include Ometria code, such as:
-
Ometria preference centre
- via API
- via CSV upload.
When you send Ometria a contact listing with @force_optin=TRUE, the marketing_optin value (explicitly opted-in or explicitly opted-out) is accepted regardless of data in any other listings for that contact.
This means that if a contact has a listing with @force_optin=TRUE, an update without @force_optin (e.g. from a third party platform) won't override their subscription status.
This means that in some cases a subscribe event from an ecommerce platform won't update the contact's subscription status due to a previous @force_optin=TRUE unsubscribe event.
Example:
In this case, the contact is being force subscribed to receive marketing communications:
"@force_optin"= TRUE, "marketing_optin"= "EXPLICITLY_OPTEDIN"
And in this example, the contact is being force unsubscribed from marketing communications:
"@force_optin": TRUE, "marketing_optin": "EXPLICITLY_OPTEDOUT"
When to use @force_optin
We recommend only including @force_optin in your API requests if you want the listing to affect subscription, i.e. when you are also sending marketing_optin.
If you don't fully trust the listing, you should either:
- Avoid using the
@force_optinflag, or; - Where possible, exclude opt-in data from the payload altogether.
How to send listings with @force_optin to Ometria
Add @force_optin=TRUE to your contact listings as a top-level parameter.
You can override the contact's subscription status by removing @force_optin=TRUE listings.
Non-force opt-in logic
If @force_optin=TRUE isn't passed, Ometria prioritises opt-out statuses.
This means that if the contact has no listings with @force_optin=TRUE and at least one listing with "marketing_optin": "EXPLICITLY_OPTEDOUT", they will stay opted-out even if you send "marketing_optin": "EXPLICITLY_OPTEDOUT".
If none of the contact's listings contain any opt-in data, their subscription status is set to unknown.
Enhanced force opt-in
If you're using Ometria's enhanced force opt-in feature, the logic works a little differently.
In this case, when a contact has at least one listing with @force_optin: TRUE, Ometria will only process subscription data for that listing.
How it works
When you have enhanced force opt-in enabled for your account, Ometria follows this process when receiving contact listings:
- Looks for opt-in and opt-out events from all listings with
@force_optin: TRUE. - Sorts those events chronologically based on timestamp.
- Checks the timeline for any changes to subscription status and records only the most recent opt-in change and most recent opt-out change.
- Compares these two timestamps and applies the most recent change as the contact's subscription status.
Removing @force_optin=TRUE listings
To remove the forced opt-in from a contact's listings, you can:
- Send an updated listing with
@force_optin=FALSE - Send an updated listing with no
@force_optinfield
@force_optin=TRUE or marketing_optin field, their opt-in/subscription status is Unknown.See also: Cross-channel marketability
Comments
0 comments
Article is closed for comments.