Facebook Web

Follow
Avatar
Travis Simpson
Updated

This article details how to configure Singular mobile, PC and Console install attribution for Facebook web campaigns (non-app campaigns). For directions on configuring and attributing Facebook app campaigns, see our Facebook (Meta) Ads Attribution guide.

Facebook campaigns do not support third-party impression URLs so all conversions are measured with click-through attribution only. 

Overview

Singular’s web-to-app attribution solutions empower marketers to run web campaigns that drive app installs across Mobile, PC, and Console platforms. Singular's Facebook web integration supports the Direct to Store flow described in our Web to App Guide here.

Add Facebook Web Partner Configuration in Singular

Add Facebook Web Partner Configuration in Singular

  1. Ensure you have an integrated web, PC, or console app with Singular
  2. Go to Singular > Attribution > Partner Configuration
  3. Click “Add a Partner”, and type and choose “Facebook Web”
  4. In the dialog, choose your App and App site (platform) to configure. Mobile, PC, and console apps are supported with this integration
  5. Paste in your app's "Access Token" and "Dataset ID" from your Meta Event Manager dashboard.


  6. Optionally configure any additional events to send to Meta and map it to a "Meta Event Name"


  7. Click "Save" to finish.
Create Singular Link for "Facebook Web"

Create Singular Link for "Facebook Web"

  1. Go to Singular > Attribution > Manage Links
  2. Select your mobile app from the list of apps on the left
  3. Select "Create Link" -> Link Type "Partner" -> Source Name "Facebook Web"
  4. Continue through the step-by-step link creation. 
  5. Click "Generate"
  6. Copy the "Click-through Tracking Link" for the next step
Set up your Facebook Web Campaign

Set up your Facebook Web Campaign

  1. In Meta Ads Business Manager, create a campaign and select either the Sales or Traffic campaign objectives:
    • Sales - optimize from events that you've set up in your Singular Partner Configuration
    • Traffic - optimize to clicks
  2. Set Conversion location to Website
  3. Add Singular Link from the section above to the Destination Website URL
  4. In the Tracking section, select the Website events from your dataset to track in your campaign

FAQ

Where can you find the Meta Dataset ID?
  1. Navigate to the Meta Event Manager.
  2. Under "Data Sources", select your web/PC/Console data source

    If this is a new data source, create a new Data Source via "Connect Data Sources" and follow Meta's step-by-step guide to create a "Web" data source. Read more about Meta data sources here.
  3. Under "Settings", copy your "Dataset ID"
Where can you find the Access Token?
  1. Navigate to the Meta Event Manager.
  2. Under "Data Sources", select your web/PC/Console data source. 


    If this is a new data source, create a new Data Source via "Connect Data Sources" and follow Meta's step-by-step guide to create a "Web" data source. Read more about Meta data sources here.
  3. Under "Settings", scroll down to "Conversions API" and under "Set up direct integration" generate and then copy the access token.

What data does Singular send via API?
Parameter Details
event_name
  • A standard event or custom event name. This field is automatically mapped to the Singular Event Name. This value is used to assist META in the deduplication of events. The event_id parameter is also used in deduplication.
fbc
  • Facebook click ID
  • automatically passed
hashed email
  • Optional
  • Hashed email may be passed as a Singular instrumented event attribute "ehash"
  • Hashed email value must be normalized and SHA 256 hashed
hashed phone number
  • Optional
  • Hashed phone number may be passed as a Singular instrumented event attribute "phash"
  • Hashed phone number must be E164 normalized and SHA 256 hashed
hashed first name
  • Optional
  • Hashed first name may be passed as a Singular instrumented event attribute "fnamehash"
  • Using Roman alphabet a-z characters is recommended. Lowercase only with no punctuation. If using special characters, the text must be encoded in UTF-8 format.
  • Hashed first name be SHA 256 hashed
hashed last name
  • Optional
  • Hashed last name may be passed as a Singular instrumented event attribute "fnamehash"
  • Using Roman alphabet a-z characters is recommended. Lowercase only with no punctuation. If using special characters, the text must be encoded in UTF-8 format.
  • Hashed last name be SHA 256 hashed
IP address
  • The Client IP Address
user agent
  • (For web only)The user agent for the browser corresponding to the event
For Deduplication of Events (Optional)  
event_id
  • Required Parameter for Deduplication
  • Pass the event_id value to Singular in the Event Arguments using an attribute name: "eventId".

Meta Requirements:

  • The event_id parameter must by added to your events from both the Conversions API and the browser Pixel.
  • The event_id parameter is an identifier that can uniquely distinguish between similar events. Read more about the event_id parameter.
What are the limitations of Meta Conversions API?
  • Meta recommends that the Meta Conversion API be used to augment an existing Meta pixel implementation.
  • For mobile integrations, Meta and Singular recommend passing mobile conversion data through Singular's dedicated mobile attribution integration with Meta. If you are interested in passing mobile conversion data through Meta Conversions API, reach out to your Singular customer success manager.