The key to maximizing the effectiveness of Facebook Analytics is by sending aggregated and anonymized data so that you can learn about the behaviors of your users. By starting with accurate data, you can develop a solid understanding of you users. This topic shows you a systematic approach to designing and implementing accurate data to send to Facebook Analytics.
Sending accurate data starts with a plan that includes the goals of your website or mobile app. Here is a list of steps to systematically design your data to meet your goals.
In this step you will determine what success is for your website or mobile app. You want to define the goals of your website or mobile app. For example, the goal of the an e-commerce business that uses a website or mobile app to sell product is to ship a product that a customer selects.
If you have several goals, go through the steps for each goal. When you have the steps for all of the goals, you can then combine common steps to make implementation more efficient.
In this step you will determine the steps your user will take to get to the goal of your website or mobile app. You need to define two routes:
Here is an example of a successful route for an e-commerce website or mobile app:
The unsuccessful route is where the user does not go to the next step. You can use Facebook Analytics to determine the last step the user completed and what step was completed. Any uncompleted step before Purchase the item is considered an unsuccessful step.
As you design the route, think about what details you want to capture about the route that your users take. Consider additional data that you want to learn about the behavior of your users. This exercise leads to the way you categorize and manage your data.
For example, you can determine how a user gets to an item from the search feature. You can capture the search terms entered, the results of the search term, the item selected, and then the items added to the cart.
Think about how you would capture the journey of the user through your website or mobile app. How would you capture each step in the journey?
In this step, you will create the data that you will send to Facebook Analytics that describes each step of a successful route. You can send two types of data:
Events and parameters describe the action a user completes along with the data in the action. An event is the action that the user completes and the parameters for the event contain the data associated with that event.
Events are broken down into three categories:
When planning out your events and parameters, see if a standard event will work for your application. The following are the standard events
Log this event when the user has achieved the level in the app.
Log this event when the user clicks on an advertisement.
Log this event when an advertisement appears to the user.
Add Payment Info
Log this event when the user has enters payment information as part of the checkout process.
Add To Cart
Log this event after the user adds an item to their cart.
Add To Wishlist
Log this event after the user add an item to their wish list.
Log this event after the user completes registration in the app or website.
Log this event after the user completes a tutorial in the app or website.
Log this event after the user submits their contact information.
Log this event after the user modifies a product selection using your tool to modify a product.
Log this event after the user donates funds to your organization or cause.
Log this event after the user finds one of your locations with an intention to visit. For example, when the user selects a button that displays the closest store with the product in stock.
Log this event after the user starts the checkout process.
Log this event after the user uses your own purchase method to complete a purchase. If you use Facebook to manage your in-app purchases, the purchase events are automatically logged.
Log this event after the user gives a rating.
Log this event after the user makes an appointment to visit your location.
Log this event after the user performs a search within the app.
Log this event after the user has spends their app credits.
Log this event after the user chooses to start a free trial of your product or service.
Log this event after the user submits an application for a product, service, or program.
Log this event after the user subscribes to a product or service.
Log this event after the user unlocks an achievement in the app.
Log this event after the user views a form of content in the app.
If none of the standard events will work for you, then you can use a custom event. Each custom event you create can have up to 25 parameters that you can also define. You can create up to 1,000 custom events.
Although you can create up to 1,000 custom events, you should create the minimum number of custom events to make data management easier. One way to create the minimum number of custom events is differentiate events by using parameters instead of create an event for each action.
For example, if your website or mobile app has several menu items, use a single event to log the action of choosing a menu item and then use a parameter to describe the menu item.
The example e-commerce website and mobile app has several steps to a successful route. The following is an example of how to use events to describe each step.
|Step||Event Name||Event Type|
Open the web page or install and start the mobile app.
Search for an item.
Add an item from the search results to a wish list.
Add to wish list
Move an item from a wish list to a shopping cart.
Add to cart
Start the checkout process.
Complete the registration.
Purchase the item.
Review shipping information when the item has shipped.
Do not send personal identifiable information (PII) or any data that has a 1:1 relationship with a user in a parameter.
You can create segments based on what you know about your users by using user properties. A user property is a value that you assign to a user who meets a specific criteria. For example, you can create a user property to track a user to a loyalty program. The values in the property can be Gold, Silver, or Bronze, depending on how much the user has bought using your app.
You can have up to 100 user properties.
Do not store personal identifiable information (PII) in a user property.
After you create your events and parameters and user properties, create a data dictionary that documents this data. The data dictionary can help you and your organize keep track of your data so that your organization sends the right data to Facebook Analytics.
For example, the Purchased standard event has the following parameters:
You use this standard event to log each item in the shopping cart that was purchased.
The data dictionary would have the following entry:
Price of the item
The price of the item when added to the shopping cart.
The currency of the price of the item.
The item name, description, color, and size.
Key-value pair as strings
In this step, you will implement the events and parameters and the user properties you defined in the previous step in your website or mobile app.
To implement an event and the parameters, use the code configurator to generate the code to add to the appropriate section of your code.
To implement a user property, see User Properties