When a user clicks the tab of a Facebook application, it is displayed in a space which is 810 pixels wide. Adobe Campaign uses a Facebook type web application to let you define and personalize the content displayed in the Facebook application, therefore making it easier to acquire profiles.
It is also possible to integrate Adobe Campaign with a Facebook application developed by a partner. In this case, there is no need to use the Adobe Campaign web application to acquire Facebook profiles. For more on this, refer to Configuring external accounts.
Please comply with the configuration steps described in Creating a Facebook application.
This section details the elements linked to Facebook type web applications. All elements shared with standard web applications are detailed in this section.
The examples of Facebook type web applications detailed here are:
These simple use cases are provided as examples to illustrate the functionalities of Facebook type web applications.
The following limitations are linked directly to Facebook:
This example provides a step by step process of how to display an Adobe Campaign built application in Facebook. In this case, we want to create an application that lets you display the Welcome message when the user clicks the application tab (App01).
To create this application, apply the following steps:
Create a Facebook Connect type external account and enter the parameters of the Facebook application. For more on this, refer to: Configuring external accounts.
Create a Facebook type web application in Adobe Campaign. For more on this, refer to: Creating a Facebook type web application.
Edit your web application. In this example, we have added a Page activity and defined a title for it.
Deploy your application.
Configure your Facebook application so that it shows up as a tab on your Facebook page. For more on this, refer to: Configuring Facebook tabs.
Check that the tab of the App01 application shows up on your Facebook page. Clicking it should call up a Welcome message.
Comply with the configuration steps detailed in Creating a Facebook application.
In example 1, we personalized the display of the Facebook page according to the value in the Fan of the page field. It is also possible to process the Application settings field. This field lets you recover data contained in a link generated by Adobe Campaign, via Facebook.
Let’s take the example of a company which decides to send an email campaign. In the delivery, a link points towards the Facebook application. This link is personalized thanks to the app_data parameter added at the end of the URL. The value of this parameter could be an indicator which reflects customer significance. In our example, the values of the app_data parameter are big (significant customer) and small (less significant customer).
Once it is personalized, the URL looks like this:
http://<path of the Facebook application>&app_data=big(for a significant customer)
http://<path of the Facebook application>&app_data=small(for a less significant customer)
Among the anonymous data forwarded to Adobe Campaign by Facebook, the value of the Application parameters field is collected, thus enabling Adobe Campaign to personalize application display based on this parameter.
If the user is a significant customer (the value of the app_data parameter is big), the following image is displayed:
If the user is a less significant customer (the value of the app_data parameter is small), the following image is displayed:
To recreate this use case, we have created a web application made up of the following elements:
Comply with the configuration steps detailed in Creating a Facebook application.
This example shows you how to get in touch with Facebook users and offer for them to share their profile information. Let’s take the example of a company which wants to acquire prospects and organizes a competition on their Facebook page to attract them.
Whenever a user clicks the App03 tab, we ask them if they want to take part in the competition.
If they decide to take part in the competition, we offer for them to share their profile information.
If they agree to share their information, the following screen is displayed.
To build this use case, we have created a web application which includes the following elements:
The Test activity is based on the ID and Application parameters field.
It is made up of three branches:
To sidestep the display error linked to Facebook, you also need to select Parent window or In the top window in the Window field of the competition page.
The Access control activity lets you display the Facebook permission request page when the user enters the competition. If they agree to share their information, it is recovered during pre-loading. For more on this, refer to: Pre-loading activity.
If you previously entered the external account when creating the web application (refer to Creating a Facebook type web application) you don’t need to edit the activity. If not, go to the Application field and select the external account linked to the Facebook application.
Select the data source to be used for pre-loading:
This option lets you recover the data of a profile which exists in the visitors table. Verification is carried out based on the external Facebook ID recovered when the user clicks on the Facebook application tab. If you add a form after the Pre-loading activity, the fields which contain information in the database are pre-loaded.
For more on pre-loading data via the Adobe Campaign database, refer to this section.
This option lets you define the Facebook profile information to collect, among that which the user has agreed to share, in view of saving it.
The Database information option lets you collect the following data:
You can also decide to collect the profile photo, the list of friends, email address, date of birth, interests and location by checking the appropriate boxes.
Before you click Ok, check the I agree to comply with Facebook conditions of use box.
If you check one or more boxes in the Private information section, the Facebook permission request screen will automatically display the access request for this data.
In order for you to collect the selected information, the user must agree to share it.
If you want both types of pre-loading (via Adobe Campaign and via Facebook) add two pre-loading boxes one after the other.
The Save activity lets you store the information collected during the previous stages in the visitors’ table.
If the profile already exists in the visitors’ table, their data is updated with the new data collected.
If the profile doesn’t exist in the database and the Facebook user’s email address has been collected, a visitor will be created in the visitors’ table.
In the Visitor creation folder field, select the folder which the profile will be created in. In case of a Facebook type web application, the default creation folder is Visitors.
In the Reconciliation mode field, select the reconciliation mode you want to use:
In the Mapping field, select the schema which you want to carry out the reconciliation on.
Make sure the fields of the Social networks tab are correctly entered in the delivery mapping. Delivery mappings are accessed via the Administration > Campaign management > Target mappings node.
You can select a search folder for reconciliation and a creation folder for new profiles. If the fields are empty, profiles are searched for and created in the default folder of the mapping schema.
To sidestep the display error linked to Facebook, you need to check the Use an external URL box and enter the URL of the Facebook application, followed by the app_data parameter and a value. This value will be used in the Test activity to detect whether or not the user has just entered the competition, and to display a thank you message if applicable. For more on this, refer to: Test activity.
In our example, the value used is thanks.
Just like for Twitter followers (refer to: Operating principle), recovered Facebook profiles are stored in the visitors’ table. To display the list of visitors, go to the Profiles and Targets > Visitors node.
Each Facebook prospect who agrees to share their profile information is added to the list of visitors. If the Friends box is checked in the Pre-load activity (refer to: Pre-loading activity), friends are also added.
In the Summary section of the visitor detail window, there are two possible states for the New Contact indicator:
If a green check mark is displayed, this means the visitor wasn’t reconciled with any recipients. In this case, a new profile is created in the list of recipients.
A red cross means that the visitor was reconciled with a recipient. You can click the magnifier to the right of the Recipient field to display the matching recipient.
Go to the detail window of a recipient to display the matching visitor, if applicable. Select the Others tab, then double-click the name of the visitor in the Web identities section.
The Activities screen of a visitor’s details page contains the following information:
“Open Graph” type fan activities: music played, videos watched, articles read and inferral of the applications installed (Deezer, Spotify, Dailymotion, Yahoo News, etc.)
“Likes” and comments added by the fan following deliveries sent by Adobe Campaign
pages liked by the fan
check-ins by the fan
In order for Adobe Campaign to collect a fan’s check-ins, you need to click the Subscribe button on the service configuration screen. For more on this, refer to Configuring external accounts.
The Social Marketing application also enables you to add a button to a form, for pre-loading fields using Facebook profile information. This option, which is available in all web application templates (Page type activities) is detailed in this section.
Before you start using this function, you need to create a Facebook application and a Facebook Connect type external account. For more on this, refer to Configuring external accounts.
Preload the fields of the form with data taken from the Facebook profile
You create a web form and include elements with which the user has no interaction in the pages of the form; these are static elements such as images, HTML content, a horizontal bar, or a hypertext link. Learn more about static elements in a web form in this page.
When inserting a static element, the Preload with Facebook option lets you insert a button into a form to preload fields using Facebook profile information.
When a user clicks the Fill in automatically button, the Facebook request for permission window opens.
You can change the list of extended rights when configuring the external account. If no extended rights are configured, Facebook forwards the basic profile information by default.
To view the list of extended rights and their syntax, refer to Facebook documentation.
If the user agrees to share their information, the fields of the form are preloaded.
For this use case, we have created a Web application made up of the following elements:
To add a preload button, apply the following steps:
Create a form.
Go to the same level as the fields in the form and add a link.
Enter the label and select the Button type.
Go to the Action field and select Preload with Facebook.
Go to the Application field and select the Facebook Connect type external account created previously. For more on this, refer to this page.