See: How does Ometria subscribe and unsubscribe contacts?
This is an Ometria field that is passed from forms that include Ometria code, such as:
- an Ometria preference centre
- via API
- via CSV upload.
@FORCE_OPTIN=TRUE is used to force the
marketing_optin value passed (whether the event is a subscribe or an unsubscribe) in the same contact record.
@force_optin is set to 'TRUE', this event takes precedence as the default marketing opt-in priority.
In this example, 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:
This action is added as a top-level parameter on the contact record and only needs to be sent once to perform the action.
@FORCE_OPTIN cannot be overridden by a ‘non-forced’ update (e.g. from third party platforms), meaning in some cases a subscribe event from an ecommerce platform - e.g. the contact leaves a ‘subscribe me’ checkbox selected on check out - might not be applied to the customer due to an existing
@FORCE_OPTIN=true unsubscribe event.
The only way this type of subscription event can be overridden is via another Ometria
@FORCE_OPTIN=true event - for example by updating the preference centre.
If there is no
@FORCE_OPTIN=true field passed, then the following order of precedence is used:
- Preferences centre.
- Ometria API, in-app change, CSV upload - these methods all have equal weight, and can override each other.
- Form or Ometria overlay
- Importer (e.g. Magento, Shopify)
- Third party
Please sign in to leave a comment.