To use Facebook Custom Audiences with customers, you must first integrate the User Information Tag, which is required to collect and process users’ email addresses, phone numbers, and GDPR opt-in information.
The email addresses and phone numbers passed to Insider One via User Information Tag for Facebook Ads Integration are one-way encrypted and are not disclosed to Facebook.
The following describes how to integrate User Information Tag for Facebook Custom Audiences using the Web SDK.
<script>
window.InsiderQueue = window.InsiderQueue || [];
</script>
<script>
window.InsiderQueue.push({
type: 'user',
value: {
“gdpr_optin”: true,
“email”: “sample@useinsider.com”,
“phone_number”: '+120394879878”,
}
});
</script>User Information Tag for Facebook Custom Audiences: Properties, definitions, and code
The User Information Tag includes the user properties. It can be implemented in all cases, including when the user is not logged in. Only the available properties will be filled in when the user is not logged in; keys without values will not be added to the object.
Key | Property | Type | Definition |
|---|---|---|---|
gdpr_optin | GDPR Opt-in | Boolean | User's permission for any Insider campaign, data collection and processing. |
Email Address | String | User's email address | |
phone_number | Phone Number | String | User's phone number in E.164 format (e.g. +6598765432) |
If your company obtains your users' consent in compliance with the local regulations, make sure to pass the GDPR opt-in field to Insider. If you want to stop collecting and processing the data of an identified user, GDPR opt-in field should have the false value. Insider cannot be held liable if these obligations are not fulfilled and reserves the right to seek compensation from your company.
Once the User Information Tag is integrated into your website, you can provide Insider One with the required fields (email, phone_number, gdpr_optin) whenever a user:
Logs in
Subscribes to a newsletter (e.g., through an input box on the footer)
Registers by providing their email (e.g., on the registration page)
For users whose gdpr_optin field is not defined or is false: The User Information Tag and/or the respective field should not be filled in.
Checklist for any page where the user object is present:
Insider.insiderObject.user returns on the page.
All properties are filled in when the user logs in.