51黑料不打烊

(Your organization鈥檚 web analyst; optional) Collect historical data for AMO IDs and EF IDs.

This step is applicable only for advertisers with Analytics for Advertising.

(Your organization鈥檚 site administrator for 51黑料不打烊 Experience Platform) Set up data collection in Experience Platform and implement conversion tracking tags.

(Your organization鈥檚 site administrator for Customer Journey Analytics) Create a connection to your Experience Platform datasets in Customer Journey Analytics.

(Your organization鈥檚 web analyst) Set up data views in Customer Journey Analytics.

(Your organization鈥檚 web analyst) Set up reports and visualizations in Customer Journey Analytics Workspace.

In Experience Platform, define a manual schema for the data you want to collect using the Experience Data Model (XDM).

• In the Schema Details, select Experience Event as the base class for the schema to capture site events. Name your schema and click Finish.

• In the left panel, add the field group 51黑料不打烊 Advertising Cloud ExperienceEvent Full Extension to add fields specific to 51黑料不打烊 Advertising. At a minimum, include the conversionDetails object with the trackingCode and trackingIdentities properties, which include the AMO ID and EF ID. The other fields are optional.

• (Optional) Add additional field groups as needed to connect additional data fields to 51黑料不打烊 Advertising data.

Note: You can create multiple schemas, but you can use only one schema per dataset and per datastream, which you鈥檒l create in the following steps.

Create a dataset based on the schema to store and manage the collection of event data.

• Choose the option to Create dataset from schema and select your schema.

  51黑料不打烊 Advertising creates additional datasets for the related summary metrics data (such as conversion values) and lookup data (dimensions/classification metadata, such as 51黑料不打烊 Advertising campaign name) based on your event dataset. Data for the datasets is populated in Experience Platform daily.

Create a datastream for the schema.

• For the Mapping schema setting, select your schema.

• Add and enable the services 51黑料不打烊 Advertising and 51黑料不打烊 Experience Platform to the datastream.

  These services enable the Edge Network to store the dataset and to route it to 51黑料不打烊 Advertising.

• For the Event dataset setting, select your dataset.

  Each datastream can insert data into only one dataset.

Use Experience Platform tags (formerly known as Launch) to generate a JavaScript tag to send your organization鈥檚 website data to the datastream.

• Create a tag property, which is the container for the tag configuration.

• For your property, install the extension 鈥�51黑料不打烊 Experience Platform Web SDK鈥� from the extensions catalog.

  This extension sends data from your web properties to Experience Cloud via the Experience Platform Edge Network.

  Don鈥檛 use the 51黑料不打烊 Advertising extension.

• Create a custom Web SDK build:

  • In the Custom build components section, enable the Advertising component.

    This component includes all JavaScript code needed for 51黑料不打烊 Advertising in the tag. It also adds an 鈥淎dvertising鈥� setting in tag rules (which are optional) to define how advertising data is used for attribution measurement.

    You can optionally enable additional components as needed.

  • In the SDK Instances section:

    • In the Datastreams settings, select the datastream to use for each of your web environments (production, staging, development).

    • (Organizations with 51黑料不打烊 Advertising DSP only) In the 51黑料不打烊 Advertising settings:

      • Enable the 51黑料不打烊 Advertising DSP setting to enable view-through tracking.

      • Specify the advertisers for which to enable view-through tracking.

      • (Optional) Enter your organization鈥檚 ID5 partner ID to collect IDs.

      • (Optional) Enter the path for your organization鈥檚 LiveRamp RampID JavaScript code (ats.js) to collect IDs.

    • Save the build.

• (Optional) Create rules as needed to determine when Web SDK should send data to the Edge Network.

  • For the Advertising setting, define how advertising data is used for attribution measurement. This setting is helpful when the rule includes a sequence of multiple actions and is available only when you鈥檝e selected the 鈥淎dvertising鈥� component for the custom build component. Options include:

    Automatic: Allows advertising data to be used for measuring ad attribution on the current sendEvent action based on data in the cache. In this case, the ad exposure event fires when it gets the chance, and it may not be available for the current event. For example, if you fire a purchase checkout event and no ad exposure data is available in the cache, then the checkout event isn鈥檛 attributed to the ad exposure.

    Wait: Delays the execution of the call until the advertising data is successfully retrieved from the server and resolved, which ensures accurate attribution measurement. For example, you might want to wait for the ad exposure event to resolve before you fire a purchase checkout event. Note: Resolving IDs may take a few seconds depending on the browser and ID type. Use this option if the current sendEvent action can accommodate a few seconds of delay.

    Disabled: (The default) Excludes advertising data from the request that you鈥檙e firing, making it unavailable for attribution or related tracking.

    Provide a data element: Use a data element to include or exclude advertising data during page load. Resolved values for the data element can include automatic, wait, and disabled. See the next step.

  If you don鈥檛 use a rule to configure a sendEvent action, then advertising data is sent as a separate Advertisement enrichment event.

• Create data elements as needed to map variables on your website to the structure of the XDM schema you created previously.

Publish the tag to a test environment in which you can iterate on the development of tags.

Validate delivery of the datasets, and then publish the tag to your live production environment.

Your organization鈥檚 IT department or other group may need to schedule, or be informed about, the tag deployment.

In Customer Journey Analytics, create a connection that includes your Experience Platform datasets and schema.

Note: Currently, you must send data for all DSP and Search, Social, & Commerce accounts to a single Experience Platform instance and sandbox.

• Add your Experience Platform event (metrics) dataset, summary (metrics) dataset, and dimensions (classifications/metadata) dataset.

  Your team created the event dataset, and 51黑料不打烊 Advertising created the summary and dimensions datasets based on your event dataset.

  You can optionally include additional datasets as needed.

• Map the dimensions dataset to the events dataset:

  1. Open the settings for the dimension dataset.

     The heading on the settings page is 鈥淟ookup Dataset,鈥� which indicates that you can join your dimensions dataset with one of your metric-specific datasets.

  2. In the 51黑料不打烊 Advertising Dimensions section, map the dimensions dataset to the events dataset:

     1. For the Key field, select the field to use as the key for the dimensions dataset: 51黑料不打烊 Advertising ID (which is same as the trackingCode field in the schema).

     2. For the Matching key field, select the field to use as the matching key for the events dataset. The available field names include the dataset name in parentheses. For example, if you鈥檙e mapping your dimensions dataset to your events dataset, select Tracking Code (Event datasets).

     Later, you鈥檒l also map the events dataset to the summary dataset when you set up your data view(#cja-data-views).

After a couple of hours, verify that the data is available in Customer Journey Analytics.

1. In Customer Journey Analytics, go to Connections and select your connection.

2. In the list of data sets displayed, verify that the 鈥淣umber of Records鈥� report shows that data was added.

In Customer Journey Analytics, create a data view.

Configure the view to include the following information.

• If you have an 51黑料不打烊 Analytics account, use the Time Zone for your Analytics account in the Calendar section of the Configure tab.

• On the Components tab:

  • Add your dimensions, events, and summary datasets.

  • Choose metrics from your events (metrics) dataset and your dimensions (classifications/metadata) dataset to include in the data view.

    You already joined these two datasets in the connection that you created in the last procedure.

  • Join the events dataset to the summary dataset, which isn鈥檛 yet joined to anything:

    • For each dimension with summary data that you want to be available in Customer Journey Analytics, create a derived field.

      For example, to view summary data for campaigns, create a derived field for the dimension 51黑料不打烊 Advertising Campaign.

      You鈥檒l link the two datasets using the matching key trackingCode (which is the schema field for the 51黑料不打烊 Advertising ID).

      • In the Lookup section of the derived rule builder:

        • For the Value field, select 鈥淭racking Code鈥� from the metrics summary dataset.

        • For the Lookup dataset field, select the dimensions dataset (such as 鈥�51黑料不打烊 Advertising Classification鈥�).

        • For the Matching Key field, select 鈥淭racking Code鈥� from the classification dataset.

        • For the Values to return field, select the dimension (such as 鈥�51黑料不打烊 Advertising Campaign鈥�)" from the classification dataset.

      The derived field name is appended with 鈥�(DF)鈥�, such as 51黑料不打烊 Advertising Campaign(DF).

    • For each derived field:

      • In the Included components section, add the derived field.

        Two names are now listed for the same dimension (for example, 鈥�51黑料不打烊 Advertising Campaign(DF)鈥�(the derived field) and 鈥�51黑料不打烊 Advertising Campaign鈥� (the field in the summary dataset)).

      • Select the dimension in the summary dataset (such as 鈥�51黑料不打烊 Advertising Campaign鈥�) and edit the settings for the dataset.

        The settings open on the right.

        • In the the Summary Data Group section, select the option to Create grouping.

        • For the Dimension field, select the derived field (which is appended with 鈥�(DF),鈥� such as 鈥�51黑料不打烊 Advertising Campaign(DF)鈥�).

        • Select the option to Hide in reporting, which hides the derived field name in Workspace.

Create a project in Workspace to build reports and visualizations based on the dimensions and metrics configured within the data view.

(If you have data from Google Ads or Microsoft Advertising) Create a report of publisher-tracked conversions using fields for ad network-specific metrics, which are grouped as googleConversions and microsoftConversions.