Deliver Offer Integration

Users create offers in Centralized offer management system and associate those offers with Deliver Email communication.

Prerequisites
  • Create Offers in Centralized Offer Management (COM)
  • Create Email communication with Offer in Unica Deliver.
  • Create Email communication with offers for each email touch point that you configure using Unica Deliver. For more information on creating Unica Email communications with Offers for Unica Deliver, see Unica Deliver User Guide.
To configure an email touchpoint with Deliver, complete the following steps:
  1. In the Email Configuration dialog, select Deliver.
  2. Click on Next.
  3. The Select Template dialog appears.
  4. Landing page - On Journey canvas, user can configure email with Deliver. If that email template in deliver has landing page associated with it then user should be able configure Journey data definition fields with Landing page fields and when end user provides any input, as per mapping fields user input will be available in Journey. User can use them in decision split.
  5. Offer Configuration - Select the required email communication. If there are multiple email communication, use the Search bar to locate the required email communication. Email communication having offers associated will be displayed on the right side of the screen along with the number of offers configured in that email communication. Example if one offer is associated with the email communication then 1 Offer will be displayed. When user hovers on Offer, then offer code and offer expiry date details appear. When user clicks on the Offer, then Offer details screen appears.
  6. Click on Next.
  7. The Mapping dialog appears.
  8. Personalization Fields Mapping - Map the Deliver fields with the appropriate Journey fields (coming from the Data Definition associated with the Journey during Journey creation). This is essential as the mapping changes the value on runtime. The mapping achieves personalization to the email. In Deliver, if you map FirstName of Deliver to fname of Journey and the LastName to lname, the salutation in the email will be personalized to the value of the field.
  9. Landing Page Response Mapping - Map the Journey fields with the appropriate Landing Page fields. When user gives the input using Landing page, then based on mapping fields user input will be available in Journey.
    Note: Journey would not be able to recognize the Landing Page form fields name by its Label Name - Journey can only recognize the Landing Page from fields by their Report Field Name attribute.
  10. Click on Save.
Points to Consider
  • If two landing pages attributes mapped in Email communications, one of the Landing page attributes are not getting in Journey.
  • If user do modify the Landing page, then for getting these changes available in Journey user needs to republish the Landing page and Email communication, do copy of email communication and by pausing the Journey do reconfigure this copied email communication.
  • If any change is made in deliver communication, then user needs to reconfigure email touchpoint to get the changes reflected in Journey.
  • If an email template having offers assigned is associated in Journey, then Journey will fetch those offers and the responses received from the emails are captured in Contact and response history.
  • User would need to use the offer template which has Offer effective and expiry date provided as fixed dates and not the flowchart run date / number of durations after effective date.
  • Unica Journey does not adhere to the Effective and Expiry dates while evaluating/ sending offers to the communication channels. User would need to manually remove the offers expired and assign active offers.
  • If Journey partition setting for the corresponding Journey is not saved, then in that case contact history and response history (CH/RH) will not be captured for the associated offer. If user proceeding without saving the journey partition, then a warning message is displayed saying You don’t have partition settings saved for journey. To save the response history and contact history (CH/RH) it is important to save partition settings in journey. You can save the settings from the settings menu.
  • For a Journey, if an offer attribute with visibility rule is assigned with deliver email template, then Journey does not support tracking the CH/RH for the offers with visibility rules.
  • If an email template having offers assigned is associated in Journey, then Journey will fetch those offers and the responses received from the emails are captured in Contact and response history database tables of Unica Campaign.
  • If there is any change in offer attribute on deliver side after associating the Deliver email-communication to Journey touchpoint, then this will not reflect in Journey. Deliver- offer association with Journey is Read Only. Offer attribute mapping is not supported for data-definition field screen.
  • In Journey we are not supporting all the offer functionality, which is supported in Deliver with batching. The plain vanilla thing for offers supporting in Journey-Deliver.
  • Journey tracks the link clicks and Linkurl which user clicks in Deliver email. These links can be used in Journey engagement split and can also be used to track the goals progress. Unlike Offer click-through links will only be captured by Journey for response tracking purpose only. These offers click-through urls will not be available in Journey engagement split and for Journey goals calculations. Links available in Deliver emails for Offers will not be listed on Engagement split page and Goals page for link click events. On Goal historical page, for non-frequency based link click goals, offer links URLs will not be available in Link drop down. Deliver "Link Clicks" count of offer links will be added as a part of total link click count for non-frequency based link click goals.
  • Journey Deliver offer integration is not supporting Offer attribute value modifications, If this offer is in use then these modified offer attribute values will not be available in Journey.
  • Journey allows duplicate records. Whenever an audience enters an email touchpoint in Journey, it will receive an offer. This offer will be reported as a contact in Campaign's Contact history tables. When the same audience ID re-enters the same email touch point, the same offer is presented once again to that audience ID. When this duplicate contact is posted to Campaign, it discards the duplicate contact record stating- The contact for same customer with same offer is already reported. In such case where Journey allows duplicate records to enter Journey, the offers (contacts) that are presented only for the first time are captured. Subsequent contacts for the same audience ID with same offer are discarded. If user does not want same audience to process multiple times, then it is recommended that user should select Do not allow duplicate contacts radio button in Journey settings. If user pushes same audience multiple times in same Journey, then only first contact is recorded. Subsequent contacts for the same audience ID with same offer are discarded.
  • Not all Centralized Offer Management attributes are supported on Deliver side for offer integration.

    Following offer attributes are supported when offers are assigned in Deliver email communication and responses are recorded in Journey :

    • Standard Attributes
      • Average response revenue
      • Channel
      • Channel type
      • Cost per offer
      • Creative URL
      • Effective date and expiration duration
      • Fulfilment cost
      • Interaction Point ID
      • Interaction point name
      • Offer Fixed Cost
    • Custom Attributes
      • Text field – String
      • Text field – Numeric
      • Text field – Date
      • Text field – currency
      • Select box – String
    Following offer attributes are not supported when offers are assigned in Deliver email communication:
    • Boolean
    • Integer
    • URL
    • Rich Text
    • Select box- Database
  • If a user tries to delete an offer for which Contact/Response history is already populated through Journey-Deliver offer integration, then that offer gets retired in COM upon deleting. Hereafter, if user pushes new audiences, then Contact/Response history will be generated for these audiences even though the offer is in retired state.
  • If a user configures deliver touchpoint with an offer but the Journey is still in Draft state (not published), then user will be able to delete this Offer from COM. Hereafter, user can publish the Journey. Emails will be sent to the audiences but Response History will not be generated in Campaign.
  • When you configure Email and SMS deliver touchpoint, you can see the preview of the communication from Journey. You can access this from the communications list used for verifying the selected communication. The preview gives you an idea of how the end-communication looks like before executing the Journey.
    Note: Only the communications created in Deliver Quick Builder are rendered as thumbnails in the communication listing screen.
  • Journey Deliver offer integration does not support COM offer variations and Offers without template.
  • In Journey Deliver offer integration, Journey is not capturing OfferUrl and OfferstaticAttributejson information hence these columns is shown as Null in Journey database offermetadata table. Journey is not supporting COM static attributes.
  • If user is unable to see Offer Code and Offer Expiry on tooltip, then they need to increase token validity in platform (set validity to 1800 on Platform > Settings > Configuration > General > Miscellaneous > Token lifetime). After increasing token validity in platform restart Platform and Offer application.