Back

This article describes how to set up the Facebook Offline Conversions connector in your Universal Data Hub account.

For more information, see Facebook Offline Conversations API.

Table of Contents Placeholder

This Facebook Offline Conversations connector allows you to send offline conversion events to see how many customers viewed or clicked on Facebook ads before converting.

Connector Actions

Action Name AudienceStream EventStream
Send Conversion

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Access Token
    • Required
    • Access Token of the Facebook System User who has access to the Ad Account and to the Offline Event Set.
  • Business Manager ID
    • Required
    • This value can be found on Facebook Business Manager > Business Settings > Business Info > Business Manager Info page.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Conversion

Parameters

Parameter Description
Offline Event Set
Content IDs
  • List of product identifiers.
  • Required for Dynamic Ads.
Content Type
  • Any valid Dynamic Ad content type, such as product.
  • Required for Dynamic Ads.
Currency
  • Three-letter ISO currency code.
  • Required for the "Purchase" event.
Event Name
Event Time
  • Required
  • UNIX-style numeric timestamp of the conversion event, for example: 1456870055.
Item Number Unique identifier to distinguish events within the same order or transaction, such as 1 or a.
Namespace ID
  • Numeric scope used to resolve third-party User ID or Lead ID.
  • See also Match Keys.
Order ID Unique identifier or receipt for each transaction or order in an offline event set, such as ATN10001.
Upload Tag
  • Required
  • String to track event uploads, for example "monthly" or "in-store uploads".
Value
  • Monetary value of conversion event
  • Required for the "Purchase" event.
City
  • Lowercase
  • No punctuation or spaces
Country 2-letter country code in ISO 3166-1 alpha-2 format.
Day of Birth DD from 01 to 31.
Email Address
  • Identify a user based on their email address
  • Address is converted to lowercase.
First Initial
  • Lowercase
  • No punctuation or special characters.
  • In UTF-8 format.
First Name
  • Lowercase
  • No punctuation or special characters.
  • In UTF-8 format.
Gender
  • m for male
  • ffor female
  • Uppercase values are converted to lowercase.
Last Name
  • Lowercase
  • No punctuation or special characters.
  • In UTF-8 format.
Lead id from Lead Ads The value of the Lead ID
Mobile Advertiser ID Specify value of either Apple Advertising ID or Android Advertising ID to target a mobile user.
Month of Birth MM from 01 to 12.
Phone Number
  • Identify a user based on their phone number.
  • Prefix the phone number with country code if "Country" field is not specified.
  • Symbols, letters, and any leading zeroes are removed.
Third-party User ID ID in external system
US State
  • 2-character ANSI abbreviation code.
  • Lowercase.
Year of Birth YYYY from 1900 to current year.
Zip Code
  • Postal code.
  • Exact format depends on country.
Check this box if the Target User Identifier Data is already hashed Check the check box if the Target User Identifier Data is already hashed
Custom Data Properties
  • Optional
  • Custom properties not specified by Facebook
Template Variables
  • Optional
  • Supported for the Custom Data Properties section
  • Provide template variables as data input for templates.
    For additional information, see the Template Variables Guide.
  • Name nested template variables with the dot notation, for example:  items.name.
  • Nested template variables are typically built from data layer list attributes.
Templates
  • Optional
  • Provide valid JSON templates to be referenced in the Custom Data Properties section
  • Templates are injected by name with double curly braces into supported fields, for example: {{SomeTemplateName}} .
  • For additional information, see the Webhook - Send Custom Request - Trimou Templating Engine Guide.