Create Facebook Audience campaign

Limited Access

Facebook Audience is currently in beta and enabled only for limited customers. Please reach out to support@moengage.com to try it out. 

Facebook audience provides out of the box integration between MoEngage & Facebook to allow marketers to retarget users on Facebook based on behavior captured on MoEngage. Using this, marketers can sync users from MoEngage to Facebook custom audience and create ads on this custom audience on Facebook.

The entire setup requires you to have access to the following elements in your FB business account:

  • Ad account - via which Ads are created, run and analyzed. Represented via Ad Account Id
  • User - whose access token is used by App to manage ads on their behalf. Ensure that this user has admin/advertiser role in the Ad account and developer or Admin Role in the FB App.
  • FB App - to allow others to access ad account via APIs on behalf of user using his/her access token

Scope

The scope of a Facebook Audience campaign is to let you add/delete users in Facebook custom audience, so that you can send FB Ads to these users. It doesn't create/publish Facebook Ads on your behalf. The support for Facebook Audience is also available in Flows

Use Cases

1. Add users to Facebook custom audience who have not received a Push or Email.

2. Add users to Facebook custom audience who have added products to cart but not purchased and have been sent a Push.

3. Delete users from Facebook custom audience who purchased a product in last 3 days.

Facebook Audience Campaign

You can create two kinds of Facebook Audience campaigns -

1. General Campaign - Targeted to a particular user segment, it can be sent at a scheduled time - once or on a periodic basis. To create General FB Audience campaign, select Card qualification criteria as All users in segment (explained in detail below)

2. Smart Trigger Campaign - Triggered on user actions ex. when a user with a particular attribute clicks on a product, a triggered campaign will be created. To create Triggered FB Audience campaign, select the qualification criteria as Based on a trigger event (explained in detail below)

In this article, we will describe how to create these two different types of campaigns in more detail. Before you proceed further, please make sure you have configured the one-time FB settings on MoEngage dashboard.

Navigate to MoEngage dashboard and select Engage > Campaigns and select Facebook Audience from Create Campaign dropdown.

mceclip0.png

You will be redirected to Create Campaign page. Click Sync FB Audience under SMS & Connectors tab. 

mceclip1.png

Step 1: Target

Select a name that helps you identify the campaign while managing the campaigns later. Campaign names must have a minimum of 5 characters. 

User Qualification Criteria

Based on how you want to target your users, select one of the two qualification options:

1. All users in segment (General campaign):

Use this option if you want to sync users to Facebook depending on certain user properties. Go to Select Audience and choose either All users or create a segment based on certain rules. 

Example: You can create a segment of users who have not received a Push notification on Android and iOS. All the users who are part of this segment will be sent to Facebook to be added or deleted from a certain custom audience (coming up in step 2). 

mceclip4.png

 

2. Based on a trigger event (Triggered Campaign):

Choose this option if you want to target only those users who perform a certain set of events or actions. You can define these events under the If/Else conditions as explained below. 

Select the user/derived event in the "IF" condition and enter the event attributes, if required. You can enter more than one event attribute as well. Next, you can enter multiple secondary conditions in the "AND" filter and finally a time delay in which secondary conditions are checked after the "IF" trigger is hit. For eg. 

IF the user performs Added to Cart

AND has not executed Purchase (you can enter multiple executed/has not executed events here)

THEN Trigger the campaign with delay of 1 hour after "IF" action (Added to Cart here)

mceclip6.png

After you have set up the trigger conditions, create your segment filter under the All users in segment step as explained above.

Next, select whether you want to include or exclude the users part of Global control group. For more information, click here

Step 2: Audience

Ad Account ID

Select Ad Account ID. An Ad Account ID contains custom audience. And, custom audience contains users. So make sure you choose the correct Ad Account ID from the dropdown menu. 

You will notice the default Ad account ID auto-selected here. You configured the default Ad Account ID in the Facebook Audience settings page. You can go ahead and change the default selection any time. 

Add/delete users option

Next, select the operation (add users or delete users) that you wish to perform via this campaign. 

Select Custom Audience

Here you can either select an existing custom audience or create a new one. 

mceclip0.png

Use existing custom audience

We will fetch and show the list of custom audiences that exist corresponding to the selected Ad Account ID. You can see the name and description of each custom audience and select the one you wish to use. In case you are not able to find the custom audience you are looking for, make sure you have chosen the correct Ad Account ID. 

Create a new custom audience

You can also create a new custom audience on the fly and then use this custom audience to add users to Facebook. Steps to create a new audience are as follows:

1. To create a new audience, select mceclip1.png button. 

2. Add audience name & description

mceclip2.png

3. Additionally, you can also add a few more parameters as key-value pairs for this new custom audience. Make sure that the fields you add are supported via Facebook. For the list of supported fields, visit FB custom audience creation page.

4. Once you have added all the fields, click Create. You will immediately see a success message indicating the custom audience ID.

mceclip3.png

5. Click Done. You will be redirected to the main screen where you will observe the newly created audience auto-selected in the custom audience dropdown. The users will now be added to this new custom audience.

 Note

  • A custom audience can be created from multiple sources. For an existing custom audience that was created in Facebook dashboard itself, sometimes Facebook doesn't allow access to that custom audience externally. If you happen to select such a custom audience, the user add/delete calls will fail in this case.
  • It's advised that you do a test campaign to make sure you are able to access the selected custom audience programmatically (meaning, via MoEngage). If you get an error, please choose another custom audience or create a new one.
  • Facebook doesn't allow to delete users from a custom audience if the audience size is too low. FB hasn't provided a count for this. So again, it would be advised to do a test campaign and make sure delete operation is allowed for the selected custom audience.
  • As per Facebook:  You can add an unlimited number of records to an audience, but only up to 10000 at a time. Changes to your Custom Audiences don't happen immediately and usually take up to 24 hours.

Matching Identifiers

You can select one or all of the below mentioned identifiers basis which Facebook will match the user. 

  1. Device Identifiers (Google advertising identifier, iOS advertising identifier)
  2. Email ID
  3. Mobile number

By default all the three options will be selected. However, you can decide to use any one or any two of these identifiers. For Email & SMS, the default values are auto-populated with the attribute values saved in Email settings page & SMS settings page respectively.  

If you decide to use all the three identifiers, then we would make three separate calls to Facebook for every user - one for each identifier. This is to maximise the match rate with Facebook. 

To understand this better, lets consider this scenario where a campaign is targeting 3 different users:

  1. User U1: only advertising identifier exists in the system
  2. User U2: advertising identifier & email ID exist in the system
  3. User U3: all 3 identifiers exist in the system
  • Case 1: If you select only one identifier, let's say mobile number for matching users to FB, then only U3 will be sent to FB for add/delete operation. Because, for U1 & U2 mobile number doesn't exist.
  • Case 2: If you select 2 identifiers, let's say mobile number & Email ID for matching users to FB, then U2 & U3 will be sent to FB for add/delete operation. Because, for U1 both mobile number & email ID doesn't exist.
  • Case 3: If you select all 3 identifiers, then all 3 users - U1, U2 & U3 will be sent to FB for add/delete operation. Because, one or more identifiers exist for all users. 
    • Another added advantage for Case 3 is that for user 3 we will make 3 calls to FB for each of the 3 identifiers. So, at FB level if one or two identifiers fail to match, still the user will be added to FB as long as atleast one identifier match is successful.
    • This approach is the opposite of FB's multi-key matching where a user will be added to FB only if all the identifiers or keys passed in the multi-key array match with FB - providing lower match rate. 

Test Campaign

As mentioned above, its advisable to do a Test campaign once you have configured all the fields in this step.  A successful test campaign will lead to actual addition or deletion (whatever you selected in the step above) of the user in Facebook Audience.

Step 3: Schedule and Goals

In this step, set the scheduling criteria for your campaign.

Conversion goals are optional. So, if you want to add a conversion goal, use mceclip0.pngto add a conversion goal.

 Note

For FB audience campaign, we will track conversions for a user once we are able to successfully send a user's details to FB for matching. Since FB doesn't give any status about whether a user was synced successfully (added/deleted) or not, we assume a success response from FB as a proxy for successfully synced.

Was this article helpful?
1 out of 1 found this helpful