ÃÛ¶¹ÊÓƵ

[On-premise/hybrid only]{class="badge yellow" title="Applies to v7 on-premise and hybrid deployments only"}

ÃÛ¶¹ÊÓƵ Analytics Connector provisioning adobe-analytics-connector-provisioning

CAUTION
These steps should only be carried out by Hybrid and On-premise implementations.
For Hosted and Campaign Managed Services implementations, please contact team.

The integration between ÃÛ¶¹ÊÓƵ Campaign Classic and ÃÛ¶¹ÊÓƵ Analytics authentication supports ÃÛ¶¹ÊÓƵ Identity Management Service (IMS):

  • If you are managing a migrated external account, you must implement ÃÛ¶¹ÊÓƵ IMS and connect to ÃÛ¶¹ÊÓƵ Campaign via an ÃÛ¶¹ÊÓƵ ID.

    Please note that the user logged in via ÃÛ¶¹ÊÓƵ ID IMS must be the owner of the Data connector account in ÃÛ¶¹ÊÓƵ Analytics and have permissions for the Product profile mentioned below.

The problem was that the owner of the Data connector was a different user than the user who was logged into Campaign and trying out the integration with Analytics.

  • If you are implementing a new connector, implementing ÃÛ¶¹ÊÓƵ IMS is optional. Without an ÃÛ¶¹ÊÓƵ ID User, ÃÛ¶¹ÊÓƵ Campaign will use a technical user to sync with ÃÛ¶¹ÊÓƵ Analytics.

For this integration to work, you have to create an ÃÛ¶¹ÊÓƵ Analytics product profile which will be used exclusively for the Analytics connector. Then, you will need to create a Developer console project.

AVAILABILITY
The Service Account (JWT) credential is being deprecated by ÃÛ¶¹ÊÓƵ, Campaign integrations with ÃÛ¶¹ÊÓƵ solutions and apps must now rely on OAuth Server-to-Server credential.
  • If you have implemented inbound integrations with Campaign, you must migrate your Technical Account as detailed in . Existing Service Account (JWT) credentials will continue to work until January 27, 2025.

  • If you have implemented outbound integrations, such as Campaign-Analytics integration or Experience Cloud Triggers integration, they will continue to work until until January 27, 2025. However, before that date, you must upgrade your Campaign environment to v7.4.1 and migrate your Technical Account to OAuth.

Create an ÃÛ¶¹ÊÓƵ Analytics Product profile analytics-product-profile

Product Profile determines the level of access a user has on your different Analytics Components.

If you already have an Analytics Product Profile, you should still create a new ÃÛ¶¹ÊÓƵ Analytics product profile used exclusively for the Analytics connector. This will ensure that your Product profile is set with the correct permissions for this integration.

For more information on Product profiles, refer to the .

  1. From the , select your ÃÛ¶¹ÊÓƵ Analytics Product.

  2. Click New Profile.

  3. Add a Product profile name, we suggest using the following syntax: reserved_campaign_classic_<Company Name>. Then, click Next.

    This Product profile should be used exclusively for the Analytics Connector to prevent misconfiguration errors.

  4. Open your newly created Product profile and select the Permissions tab.

  5. Configure the different capabilities clicking Edit and select the permissions to assign to your Product profile by clicking the plus (+) icon.

    For more information on how to manage permissions, refer to the .

  6. For the Report Suites capability, add the Report Suites you need to use later on.

    If you don’t have any report suites, you can create it following these steps.

  7. For the Metrics capability, add the Metrics you will need to configure later on.

    If needed, you can switch on the Auto-include option which will add every permissions item into the included list and will automatically add new permission items.

  8. For the Dimensions capability, add the Dimensions needed for future configuration.

    Ensure the chosen Dimensions match those to be configured in the External Account and align with the corresponding eVars number from ÃÛ¶¹ÊÓƵ Analytics.

  9. For the Report Suite Tools capability, add the following permissions:

    • Report suite Mgmt
    • Conversion variables
    • Success events
    • Custom data Warehouse report
    • Data sources manager
    • Classifications
  10. For the Analytics Tools capability, add the following permissions:

    • Code Manager - Web services
    • Logs - Web services
    • Web services
    • Web service access
    • Calculated metric creation
    • Segment creation

Your Product profile is now configured. You then need to create the OAuth project.

Create OAuth project create-adobe-io

To proceed with configuring your ÃÛ¶¹ÊÓƵ Analytics connector, access the ÃÛ¶¹ÊÓƵ Developer console and create your OAuth Server-to-Server project.

Refer to this page for the detailed documentation.

Configuration and usage adobe-analytics-connector-usage

Learn how to work with ÃÛ¶¹ÊÓƵ Campaign and ÃÛ¶¹ÊÓƵ Analytics in ÃÛ¶¹ÊÓƵ Campaign v8 documentation.

recommendation-more-help
601d79c3-e613-4db3-889a-ae959cd9e3e1