Edge Media Migration Basics

[#1]

Configuration Options

One of the questions that often comes up with the Media migrations to Edge is, “what are the configuration settings I need?”

The unspoked part of that question is, “We used to have so many, and now you’re only giving us a datastream ID”

Indeed, let’s talk about Edge vs non-Edge Media SDK implementations.

In the non-Edge implementation, you had to add a few configuration parameters to the implementation itself:

• RSID (report suite ID)
• HB End point
• Analytics end point
• Org ID/publisher
• Channel, sdkVersion, playerName
• SSL flag
• AudienceManager and target settings, as applicable
• App Environment ID (if applicable)

In the Edge implementation, the development team will only be concerned with:

• Datastream ID (aka Config ID)
• Edge End point (maybe; aka Domain Name)
• App Environment ID (if applicable)

In an Edge implementation, all data, including Media data, is sent to one unified end point so you no longer need to provide a separate video/Heartbeat server. Rest assured, you still have the flexibility to configure your implementation, but it is now done at the datastream level, rather than in the code itself.

One exception: you can no longer choose non-SSL configuration option. Edge tracking only allows for secure traffic overall, including Media data.

The table below provides an overview of all parameters applicable to Media implementations

Configuration Parameter	non-Edge Media Implementation	Edge Media Implementation
Analytics Report Suite	In the json configuration file for mobile apps part of AppMeasurement configuration in web implementations	Configured in the Datastream UI, part of the Analytics service
Heartbeat End Point	In the json configuration file for mobile apps, mediaConfig setting in JavaScript implementations	No longer required
Analytics End Point	In the json configuration file for mobile apps part of AppMeasurement configuration in web implementations	No longer required
Org ID/Publisher ID	Could be set in configuration in older Heartbeat implementation; not set in current Heartbeat implementations	No longer required; value will be implied based on the datastream configuration
Datastream	N/A	Make sure Media data is checked in the Datastream configuration
Edge End Point	N/A	Set in Tags
SSL Flag	In the json configuration file for mobile apps; mediaConfig setting in JavaScript implementations	Only SSL connections are allowed, therefore this setting is no longer valid
App Environment ID	Mobile apps only: included the same way for both Heartbeat and Edge implementations	Mobile apps only: included the same way for both Heartbeat and Edge implementations

Next Steps: UI Configuration

As we’ve pointed out, your Edge Media implementation would only require a Datastream ID, and an Edge endpoint for web implementation and only an Environment ID for mobile implementations.

The rest of the configuration is done in the UI.

First, you need to create a datastream, or choose an existing datastream. Then check the box for Media Analytics under Advanced configuration options for the datastream.

It may be a good idea to re-run the Media Analytics Wizard at this time as well. Doing so will ensure the latest OOB reports and metrics are enabled in your Analytics report suites.

Next Step: Take stock of what you currently have

Now that you have a better view into configuration differences, you need to consider the existing set up to map out your Edge migration for Media. This would include platforms, players, Media SDKs, library/extension versions and any tag management systems used. Ideally, you have a BRD and other specification documents that describe your implementation, clearly outlined test cases and a predefined QA approach.

Make sure you go over any existing reports and dashboards to check whether you have any outstanding bugs or inconsistencies in the existing implementation. 

You also need to understand how you are handling identities, including visitor identifiers, or ECID. Be aware if you need to make special considerations for sharing the ECID value between the player and the page/app itself.

Understanding the new configuration options and a clear outline of the current status will allow you to create a detailed migration plan and ensure that your transition to Edge Media is smooth and uneventful.