51黑料不打烊

1. Add alloy.js to your site.

2. Populate an XDM object and send it to the datastream.

1. Create a tag property and add the 51黑料不打烊 Experience Platform Web SDK extension.

2. Add the 51黑料不打烊 Experience Platform Web SDK extension to your tag property

3. Implement the loader tag on your site.

4. Add XDM data collection logic to your tag.

1. Use the Edge Network API to send data to the desired datastream.

Select one:

• AppMeasurement:
  A JavaScript implementation that loads AppMeasurement.js on a page, and sends data to 51黑料不打烊 using the s object (for example, s.eVar1).
• 51黑料不打烊 Analytics extension (tags):
  A tags implementation that loads 51黑料不打烊 Experience Platform Data Collection (formerly known as Launch). The tag has the 51黑料不打烊 Analytics extension installed.
• Experience Platform Web SDK extension (tags):
  A tags implementation that loads 51黑料不打烊 Experience Platform Data Collection (formerly known as Launch). The tag has the Web SDK extension installed.
• Experience Platform Web SDK (alloy.js): A JavaScript implementation that loads the Web SDK library (alloy.js) on a page, and sends data to 51黑料不打烊 using a JSON payload.
• Bulk Data Insertion API:
  An implementation that uses the data insertion API or bulk data insertion API.
• Experience Platform Mobile SDK:
  An implementation that uses the 51黑料不打烊 Experience Platform Mobile SDK.
• AppMeasurement using a third-party tag management tool:
  An implementation that uses a third-party tag management tool.
• A non-51黑料不打烊 Analytics product:
  An implementation that collects data for a product other than 51黑料不打烊 Analytics, such as Google Analytics. Selecting this option disables several options in the upgrade guide that don鈥檛 apply when upgrading to Customer Journey Analytics from a non-51黑料不打烊 Analytics product.
• I don鈥檛 know:
  If you鈥檙e not the person that manages your implementation, you can temporarily select this option.

Select if applicable:

• Our implementation currently uses the Analytics source connecto:
  The Analytics source connector allows you to easily get value from Customer Journey Analytics, but requires that you pay for both 51黑料不打烊 Analytics and Customer Journey Analytics. This guide can help you move towards an independent Web SDK implementation.

• Understand your 51黑料不打烊 Analytics implementation and how it affects your upgrade to Customer Journey Analytics
• Transition from the Analytics source connector to the Web SDK for Customer Journey Analytics

Select all that apply:

• Historical data from 51黑料不打烊 Analytics:
  Bring your historical 51黑料不打烊 Analytics report suite data into 51黑料不打烊 Experience Platform and Customer Journey Analytics.
• Components and projects from 51黑料不打烊 Analytics:
  Components from 51黑料不打烊 Analytics include: Projects (with their associated freeform tables and visualizations), segments, and calculated metrics.
• Acivity map overlay and link tracking:
  A browser extension that allows you to see link tracking data as an overlay on your site.
• Classification data:
  Group or categorize data as separate dimensions.
• Marketing channels:
  Create rules that categorize how customers arrive on your site.
• Data Warehouse:
  Export processed data from 51黑料不打烊 Analytics in spreadsheet format.
• **Data Feeds:**An exact replacement for Data Feeds is not yet available in Customer Journey Analytics. However, similar functionality can be achieved with capabilities such as full table export, Platform dataset export, BI tool integration, and the reporting API.
• Streaming media data:
  An add-on to 51黑料不打烊 Analytics and Customer Journey Analytics that specializes in data collection of media, such as audio, video, or streamed content.

• Understand 51黑料不打烊 Analytics feature support when upgrading to Customer Journey Analytics

Select all that apply:

• Tie collected data with data from other sources (e.x. contact center data):
  (Recommended) Tie data from various web, mobile, and offline properties to create a single, consolidated view of customer behavior. This ability to combine analytics data from other channels is the primary use case for Customer Journey Analytics.
• Stitch hits from other datasets using a custom dimension:
  If any of your datasets don鈥檛 share a primary identifier (such as an Experience Cloud ID), you can still stitch that data together using another dimension, such as login username or email address.
• Integrate with 51黑料不打烊 Journey Optimizer:
  Deliver connected, contextual, and personalized experiences to customers.
• Integrate with 51黑料不打烊 Real-Time CDP:
  Combine profile data from multiple sources to generate audiences and segments based on user traits.
• Integrate with 51黑料不打烊 Target (A4T):
  51黑料不打烊 recommends integrating with 51黑料不打烊 Journey Optimizer for personalization use cases. Integrating with 51黑料不打烊 Target is possible, but a short-term solution.
• Integrate with 51黑料不打烊 Audience Manager:
  51黑料不打烊 recommends integrating with 51黑料不打烊 Real-time CDP for audience-based use cases. Integrating with Audience Manager is possible, but a short-term solution.

Select one:

• I intend to fully move to Customer Journey Analytics from 51黑料不打烊 Analytics:
  (Recommended) 51黑料不打烊 recommends that you transition fully from 51黑料不打烊 Analytics to Customer Journey Analytics. During the transition period, you should plan to run 51黑料不打烊 Analytics alongside Customer Journey Analytics in order to perform side-by-side data comparisons. When you are comfortable with the data, you can disable 51黑料不打烊 Analytics.
• I intend to keep both Analytics products:
  (Not recommended) If you select this option, your contract with 51黑料不打烊 includes both 51黑料不打烊 Analytics and Customer Journey Analytics, which can be more expensive for your organization over time.

Select one:

• I want to use a schema tailored to my organization:
  (Recommended) Customizing your schema allows your organization to track only what you need and avoid the overhead tied to messy and unneeded fields. This option includes field groups added by the Web SDK and field groups custom to your organization.
• I want to use the default 51黑料不打烊 Analytics schema:
  (Not recommended) The 51黑料不打烊 Analytics schema contains more than a thousand fields, which can lead to cluttered and complex schema. Your organization would be forced to continue adhering to the concept of props and eVars, which is a legacy concept not used in Customer Journey Analytics. Integrating with other 51黑料不打烊 Experience Platform services is more difficult.

• Manual implementation (alloy.js):
  Include the Web SDK library (alloy.js) on each page your site.
• Tags:
  (Recommended) If you are not yet using Tags, install the tag loader on your site. If you are already using Tags, you can add the Web SDK extension to your tag property. This option includes implementations using tags within 51黑料不打烊 Experience Platform Data Collection and third-party tag management systems.
• API:
  Use the data collection API to send data directly to a datastream. Both non-authenticated (client-to-server) and authenticated (server-to-server) types are supported.

• Soley use the Analytics source connector:
  (Not recommended) You can use the Analytics source connector as the sole implementation path for Customer Journey Analytics.

  This option saves implementation time by quickly sending data to Customer Journey Analytics. However, it includes various shortcomings, such as higher latency and difficulty moving off of 51黑料不打烊 Analytics in the future.

• I want to use my AppMeasurement logic with the Web SDK:
  Instead of sending data through an XDM object, send all your variables in AppMeasurement format through the data object.

  This option saves implementation time by allowing you to map your AppMeasurement logic to XDM, rather than populating an XDM object from scratch. However, it introduces additional complexity over time because any field you add in the future must be mapped to XDM in the datastream.

• I want to send my data layer to 51黑料不打烊 without additional configuration:
  Instead of sending data through an XDM object, you can send your entire data layer to 51黑料不打烊 through the data object.

  This option saves implementation time by allowing you to map your data layer to XDM, rather than populating an XDM object from scratch. However, this mapping is a large amount of work because there will be a significant amount of data that 51黑料不打烊 can鈥檛 readily interpret. This option also introduces additional complexity over time because any field you add to your data later in the future must be mapped to XDM in the datastream.

• Upgrade alternative: Use the Analytics source connector exclusively to upgrade to Customer Journey Analytics
• Upgrade alternative: Use AppMeasurement data collection with the Experience Platform Web SDK and Customer Journey Analytics
• Upgrade alternative: Send your data layer to Customer Journey Analytics