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

How to migrate existing Genesis integrations to Adobe Analytics Connector acc-aa-faq

Starting Campaign Classic v7 21.1.3 release, the Adobe Analytics Data Connector is deprecated. Learn more

On August 1, 2021, Adobe Campaign Classic has been removed from the legacy Data Connectors UI, however, existing Campaign integrations will continue to collect and pass data to Adobe Analytics until August 17, 2022. After this date, the integration will cease to collect and pass data to Adobe Analytics.

You must implement the new Adobe Analytics Connector integration on Adobe Exchange which replaces the legacy Data Connectors Integration. To learn more about Adobe Analytics Connector, refer to this page.

For any questions about these changes, read the FAQ. For more information, contact Adobe Customer Care.

If you are migrating from an existing Adobe Analytics Data Connector (previously known as Genesis integration) and using the New Classification Architecture in Adobe Analytics, you need build versions starting from 7.3.1 or 8.4.1 to be able to migrate to the new Adobe Analytics Connector.

What changed?

A new integration between Campaign Classic v7 and Adobe Analytics is now available. Major changes are listed below.

  • The Contact Date Classification, which use to be of type date, has been deprecated by Adobe Analytics. For migrated integrations, it will still remain of the same type. For any Contact Date created by Campaign, the type will be String.

  • Processing Rules are created by Adobe Campaign as part of new integrations. Either Processing Rules should be created manually from Adobe Analytics or directly use Client-Side Javascript implementation. Processing Rules will remain intact for existing integrations.

  • The built-in technical workflows and their behavior remains the same. Only the backend APIs used by the workflows to push/pull data to/from Adobe Analytics have been changed.

  • Note that the nlserver process should be configured with the IMS Technical Account User for the new connector to work. This change must be done by Adobe. To have this implemented, contact Adobe Customer Care.

  • If you were Adobe Genesis APIs in customized workflows for pulling and pushing the data from Adobe Analytics, you now need to use the new Adobe Analytics 1.4/2.0 APIs. Learn more

Are you impacted?

If you are using the existing Adobe Analytics Data Connector (previously known as Genesis integration), and the integration was implemented on a lower build than Campaign 21.1.3, you are impacted.

Learn how to check your version in this section.

How to update?

You need to upgrade to Campaign 21.1.3 (or more) before August 17, 2022.

As a hosted customer, Adobe will be working with you to upgrade your instance(s) to the newer version. You will then be able to use Adobe Analytics connector.

As an on-premise/hybrid customer, you need to upgrade to one of the newer versions to benefit from the new integration.
Once all instances are upgraded, you will be able to implement the new integration to Adobe Analytics Connector, and ensure a seamless transition.

FAQ faq-aa

How can I get logs?

User interface configuration and workflows are equipped with verbose logging.

In verbose mode, request and response headers are also printed for each API request to Adobe Analytics.

As an on-premise user, you can implement the verbose mode as follows:

  • To enable verbose mode for the user interface: re-run the web process in verbose mode.
  • To enable verbose mode for the webAnalytics workflows: select the Execute in the engine option from the workflow properties, and re-run wfserver in verbose mode.

What does the ‘Integration Owner Not Admin’ error means?

Learn more about the Data Connectors Integration Owner Not Admin Error in this page.

Once migration to the new connector is done, what happens to old data and report suites?

After migration, a new connector (migrated from the old connector) will start pushing data to that same report suite and existing data will not be affected: it will be adding to the existing data.

Some existing evars/events/report suites present in Analytics are not visible in Campaign. What should I do?

Integration relies on data on Technical Account Token for day to day operation. If there is missing permission to a dimension/metric/report suite from the product profile associated with Technical Account User, APIs that we use will simply falter for those requests.

If we are reading for details of an Analytics component (like metrics/dimensions/segments/report suites), the API will not return these components in the result (which may look like something got deleted on the Analytics side or is not present). Analytics API will reject those requests and error out.

The solution is to update the Product Profile in Analytics User Context of Technical User Token with the newly created/missing components by adding these components in Adobe Admin Console. For more guidance, contact Adobe Customer Care.