Profile Portal allows certain actions to be taken on a customer profile without the need to fully log in. One of those actions is to change communications preferences. This centralised ‘Preference Centre’ ensures that comms preferences are kept in sync across all platforms and channels in real-time, allowing for different comms platforms to leverage the customer profile data in real-time while complying with permission marketing requirements.
To direct a known customer to the comms preferences section of Profile Portal from any communication they receive directly from your marketing communications tools, you must include a unique and obscure identifier to set which customer’s comms preferences are to be changed. The identifier is the customer’s Omneo Profile ID.
The ID must be added to the end of your profile portal domain address in 2 different ways.
Manage My Comms Preferences
https://my.branddomain.com/messaging?p=profile_id
This displays the Preference Centre for the current profile ID without changing any settings on load. If a customer changes their settings they are saved instantly.
Unsubscribe from all Emails
https://my.branddomain.com/unsubscribe?p=profile_id
You can also provide a direct pathway (one click) to unsubscribing via custom URL forward-slash unsubscribe. There may be limitations when using this method due to email marketing software specifications. Unsubscribe URL with the identifier:
Emarsys
Identify which Emarsys Field ID is mapped to an Omneo Profile ID. You may have this documented in a data schema or while logged into Emarys, locate the field in the Admin > Field Editor section. The numeric Field ID is required not the Field String ID. Using the Emarys Scripting Language personalisation variable the parameter should include contact as {{ contact.Emarsys Field ID }} A formed URL example:
- https://join.branddomain.com/messaging?p={{ contact.Emarsys Field ID }}
Depending on the individual configuration you may be able to include a direct link to unsubscribe using Profile Portal. A direct link to unsubscribe example
- https://join.branddomain.com/unsubscribe?p={{ contact.Emarsys Field ID }}
Salesforce Marketing Cloud
Identify which Marketing Cloud Field Name is mapped to an Omneo Profile ID. You may have this documented in a data schema or while logged into Marketing Cloud, locate the field in the Contact Builder > Data Extensions section where the sendable Data Extension being used is located. Using the Marketing Cloud AMPScript method, you would define variable then form the URL string to call the field name for example:
%%[ VAR @ Omneo Profile ID SET @url = Concat(’ https://join.branddomain.com/messaging?p=’,@Omneo Profile ID) ]%%The RedirectTo function would then be applied to the HREF as
- %%=RedirectTo(@URL)=%%
Depending on the individual configuration you may be able to include a direct link to unsubscribe using Profile Portal. A direct link to unsubscribe example would follow the same method as above
%%[ VAR @ Omneo Profile ID SET @url = Concat(’ https://join.brandrdomain.com/unsubscribe?p=’,@Omneo Profile ID) ]%%The RedirectTo function would then be applied to the HREF as
- %%=RedirectTo(@URL)=%%
Bronto
Identify which Bronto Field Name is mapped to an Omneo Profile ID. You may have this documented in a data schema or while logged into Bronto, locate the field in the Contacts > Fields section.
The Field Name will be text. Using the Bronto Message Field Tag personalisation method the parameter will be formatted with %% either side A formed URL example
- https://join.branddomain.com/messaging?p=%%Omneo Profile ID%%
Depending on the individual configuration you may be able to include a direct link to unsubscribe using Profile Portal. A direct link to unsubscribe example
- https://join.branddomain.com/unsubscribe?p=%%Omneo Profile ID%%
Mailchimp
Identify which Mailchimp Field Name is mapped to an Omneo Profile ID and locate the field in the Audience > Audience fields and *|MERGE|* tags section. The Merge Tag will be used rather than the Field Name. Using the Mailchimp Merge Tag personalisation method the parameter is wrapped in special characters: *|EXAMPLE|*. A formed URL example:
- https://join.branddomain.com/messaging?p=*|Omneo Profile ID|*
Depending on the individual configuration you may be able to include a direct link to unsubscribe using Profile Portal. A direct link to unsubscribe example
- https://join.brandrdomain.com/unsubscribe?p=*|Omneo Profile ID|*
Klaviyo
Identify which Klaviyo Custom Property (or Profile Property) is mapped to an Omneo Profile ID. You may have this documented in a data schema or while logged into Klaviyo, locate the field by opening a Profile and view the custom properties. Using the Klaviyo personalisation variable, the parameter should include contact as {{ person|lookup:‘Omneo Profile ID’ }}A formed URL example:
- https://join.branddomain.com/messaging?p={{ person|lookup:‘Omneo Profile ID’ }}
Depending on the individual configuration you may be able to include a direct link to unsubscribe using Profile Portal. A direct link to unsubscribe example:
- https://join.branddomain.com/unsubscribe?p={{ person|lookup:‘Omneo Profile ID’ }}