Meta Ads

📘

The previous Facebook Ads integration has been deprecated in favor of this new Meta Ads integration which leverages a simplified Ad Account and Dataset linking process.

There are no reporting, feature, or technical differences between the new Meta Ads integration and the deprecated Facebook integration.

If you already have a Facebook Ads tracker set up, you may continue utilizing that integration without issues.

Cost Aggregation Features

Simply linking your Meta Ads account to Gamesight will enable Cost Aggregation, which includes:

• Syncing Meta's reported Clicks, Impressions, and Cost data (alongside your other marketing channels) into your Gamesight reporting

Attribution Features

As a Gamesight attribution customer, linking your Meta Ads account to your Gamesight Tracker will enable you to:

• See Meta campaign performance alongside your other marketing channels in Gamesight
• Track which Meta ads are driving actual game installs (not just clicks), as well as any post-install goals
• Send conversion data back to Meta so their algorithm can find more players like yours (automated, install-based optimization)
• Compare cost-per-install (CPI) and return on ad-spend (ROAS) across all your marketing channels

Integration Steps

🚧

Meta Ads Account & Gamesight Data Syncing

Before proceeding with the account linking steps below, please be sure that you are using a game-specific Meta Ads Account.

This Meta integration enables all active campaigns running in your Meta Ads Account to sync back into Gamesight's reporting (including network reported impressions, clicks, and cost data).

1. Create your Meta Tracker and Link your Meta Ads Account

To create your Meta Ads tracker and link your Meta Ads account to Gamesight:

1. Click Trackers (under Measurement) on the left-hand side of Gamesight Console.

2. Click the "Create" button at the top of the page as shown below.

   

3. Next, search for "Meta" and click on the Meta logo.

   
   

4. Click "Use Meta".

5. Click the Authorize with Meta button.

   

6. Complete the oAuth flow to successfully link your Meta Ads account to Gamesight.

👍

Integration Complete!

Your integration enabling Cost Aggregation is complete!

The remainder of this documentation will only be used by Gamesight Attribution customers

Attribution - Campaign Setup

This portion of our documentation requires that your Meta Ads Tracker is created and your Meta Ads account is linked to Gamesight. Jump to the top of this documentation for a detailed walkthrough.

For each Meta campaign that you want to enable attribution for, you need to:

1. Open your campaign in Meta Ads Manager.
2. In the Ad level, find the Destination URL field.
3. Add the Gamesight Click URL from your Meta tracker (created in Step 1 above) into the Destination URL field:

Gamesight Click URL

Your Click Tracker for Meta will look something like this:

https://gsght.com/c/XXXXXX?campaign={{campaign.id}}&campaign_name=
{{campaign.name}}&ad_group={{adset.id}}&ad_group_name={{adset.name}}
&ad={{ad.id}}&ad_name={{ad.name}}

👍

Just use the Network Tracker!

You can use this same tracking link for all of your Meta campaigns. Gamesight automatically separates the data by Campaign, Ad Set/Group, and individual Ad.

Multiple Landing Pages

If you want to direct users to different landing pages, you can simply use the destination_url parameter on your tracking link to control the page.

In the example below, we're sending users to google.com instead of our default destination URL. Note the &destination_url=https://google.com/ parameter appended to the end of the tracking link:

https://gsght.com/c/XXXXXX?campaign={{campaign.id}}&campaign_name=
{{campaign.name}}&ad_group={{adset.id}}&ad_group_name={{adset.name}}
&ad={{ad.id}}&ad_name={{ad.name}}&destination_url=https://google.com/

You can read more about using the destination_url parameter in our URL Parameters & Macros guide.

Postback Conversions to Meta

Gamesight, in partnership with Meta, has created an integration for sending conversion data from Gamesight back to Meta, which enables Meta to:

• Show your ads to people more likely to install, purchase DLC, etc.
• Create lookalike audiences based on your actual players, while excluding existing players from seeing install ads

an finalize the setup for postbacks on our end.**

Postback Configuration

To set up Postbacks from Gamesight to Meta Ads:

1. Navigate to the Meta tracker in Gamesight.
2. Click Integration to verify that your Ad Account and Pixel are linked/selected.
3. Click Postbacks
4. Select a Goal trigger and enter an Event Name for your Postback.

You can create as many Postbacks as needed by repeating Steps 3-4 above.

Click here to learn more about our Postback Management tooling.

Postback Event Names

Meta provides a set of Standard Event Names that you can utilize to name your Postbacks in Gamesight. Using a Standard Event Name will require no additional work in Meta to see and utilize your postback data in your Meta campaigns.

🚧

Non-Standard Event Names

Using an Event Name that is not in Meta's list ofStandard Event Names will require you to set up a Custom Conversion Event in Meta Ads.

Custom Conversion Events

If you are using a non-standard Event Name for your postback from Gamesight to Meta, you will need to set up a Custom Conversion Event in Meta in order to see and utilize the postback data in your campaigns. To do this:

1. Open your Meta Dataset (formerly "Meta Pixel") in Events Manager
2. Click "Create > Create Custom Conversion". In the image below, you will see an example of a Custom Conversion Event.

Once you have received at least one postback with a non-standard name in your Dataset, you should be able to find the postback under the list of "Custom events" as shown in the image below.

A Custom Conversion Event requires at least 1 "Rule". The Rule can be filled out at your discretion, however you can make the Rule something simple such as: URL > Contains > .

By entering a period in the text field below "URL > Contains" you can click the "+" button on the right to add the period as a rule. The logic behind this simplified rule helps to avoid any potential issues as we know that every URL has to have a "." in it.

Additional Match IDs for Postbacks (Optional)

📘

Additional Match ID Use Cases

The following steps are only necessary if you are seeing low match rates in Meta Ads Manager or if you would like to send unattributed conversions to your Meta Dataset (formerly "Meta Pixel").

Gamesight's default configuration will include a Meta Click ID value on all Postbacks .

Gamesight supports multiple additional matching methods into the Meta Dataset. These can be helpful for increasing match rate, or to send unattributed/organic installs back to your Meta Dataset.

External ID Sync (Optional)

If you are seeing low match rates in Meta, you can set up a landing page where both the Meta Dataset and Gamesight Web SDK are placed.

Here is an example of the completed integration code:

<script>
/* Including the Meta Pixel snippet */
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window, document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
  
/* Including the Gamesight Web SDK snippet */
(function(G,m,s,g,h,t){G.gsght=G.gsght||function(){
(G.gsght.q=G.gsght.q||[]).push(arguments)},G.gsght.q=[],G.gsght.h=1*new Date();
h=m.createElement(s),t=m.getElementsByTagName(s)[0];h.async=1;h.src=g;t.parentNode.insertBefore(h,t)
})(window,document,'script','https://cdn.gsght.com/sdk.js');

/* Configuring both the Gamesight Web SDK and Meta Pixel */
gsght('init', 'GS_WEB_SDK_ID_HERE', 'web');
gsght('set', 'fb_enabled', true);
gsght('send');

gsght('onload', function(){
  fbq('init', 'FB_PIXEL_ID_HERE', {'external_id': gsght('get', 'gsid')});
  fbq('track', "PageView");
});
</script>

In the integration code above, please be sure to replace the following two placeholders with actual data.

1. Replace GS_WEB_SDK_ID_HERE with your Gamesight Web SDK ID.
2. Replace FB_PIXEL_ID_HERE with your Meta Pixel ID.

Once this code is placed on your landing or marketing page, ensure all of your Meta ads drive traffic to this page. This should increase the match rates that you are seeing in Meta utilizing our mapped external ID as well as automatically pulling in the fbp browser ID value.

Email Matching (Optional)

You can pass hashed email data as an external ID with your event integration to enable email matching on conversion uploads into Meta. Below is an example making this association in the Measurement API.

curl https://api.ingest.marketing.gamesight.io/events \
    -X POST \
    -H 'Authorization: SOMEAPIKEYHERE' \
    -H 'X-Api-Version: 1.1.0' \
    -H 'Content-Type: application/json' \
    -d "$(cat <<-EOF
  {
    "user_id": "b91f8k5r",
    "type": "game_launch",
    "ip": "172.123.245.14",
    "external_ids": [
         {
              "external_id_type": "email",
              "external_id": "f1904cf1a9d73a55fa5de0ac823c4403ded71afd4c3248d00bdcd0866552bb79",
              "sha256": "client"
         }
    ]
  }
EOF
)"

• Note that the external ID association only needs to be made once - it is not a requirement that you pass the email with every event.
• The email format must be SHA256 hash of the email, lowercase, trimming whitespace as outlined in Meta's Documentation
• If you would prefer to send unhashed emails you can use "sha256": "server" to request email hashing

IP and User-Agent (Optional)

Gamesight can be set up to transfer your users' IP addresses and User-Agent values to your Dataset, enhancing match rates. This integration involves sending an un-hashed IP address to Meta, which Gamesight typically doesn't store (we usually hash IPs upon receipt).

🚧

Contact support!

Once you have implemented one of the above strategies, please contact Gamesight Support so that we can validate the implementation and enable the data flow to your Meta Dataset. The additional IDs will not be utilized until Gamesight confirms the implementation.

Troubleshooting

In the table below, we go over some common questions surrounding Meta campaigns, performance, etc.