InBox > Integrating with Oracle Responsys

Integrating with Oracle Responsys

Oracle Responsys supports send time personalization.

Oracle Responsys has a built in Hash tokens that should be use for mapping subsribers.

&os_ehash=${EMAIL_MD5HASH}

OR

&os_ehash=${EMAIL_SHA256HASH}

Use the <#include> function to request content from OneSpot.

<#include “https://api-2.rec-engine-mail.com/recommend?AUTH_TOKEN=onespotProvidedToken&QUERY_STRING=query&CONTENT_URLS=https://sampleurl.com&FILTER_STRING=filter&RECOMMENDATION_UNIT_ID=oneSpotProvided&&BATCH_ID=${campaign.name}&MESSAGE_ID=${campaign.name}-${EMAIL_SHA256_HASH_}&EMAIL_HASH=${EMAIL_SHA256_HASH_}”>

The URL value is the URL to the OneSpot Inbox endpoint and will include several parameters. The exact URL will be produced by the InBox Wizard or supplied to you by your Customer Success Manager.

Some of the parameters include:
  • QUERY_STRING
  • CONTENT_URLS
  • FILTER_STRING
  • RECOMMENDATION_UNIT_ID
  • BATCH_ID
  • MESSAGE_ID
  • EMAIL_HASH
  • AUTH_TOKEN

At least one entry, and optionally multiple entries, need to be added to the link table for the campaign to allow clicks on the personalized content to be tracked.

To track all clicks in one bucket enter “OneSpot_Click_Tracker” as the Link_Name and “http://redirect.onespot.com/redirect?url=$CONTENT_URL$&id=$RESPONSE_ID$&channel=inbox” as the Link_URL.

To track clicks in different buckets, create other entries using the same Link_URL but a different Link_Name

Within the templates, your links should be configured as follows:
href=”$clickthrough(onespot_click_tracker,CONTENT_URL=http://www.yoursite.com?utm_source=yourSource&utm_medium=yourMedium&os_ehash=523af537946b79c4f8369ed39ba78605,RESPONSE_ID= PFRp_eUuQz2GtGjlBnHkJA)$”
If the API call does not return any content, the message will be failed and will be put into “Retry” by Oracle Responsys.