When offer activity results are displayed in the Results Window, the following are shown.
•Title: the Results Window’s title is set to 'Offer Results for Workflow ID [x]’. On hovering over the title, the current Workflow Instance ID and Offer Execution ID are shown in a tooltip.
•Results tab:
o Toolbar contains:
§ View Dynamic Content Results: this button is only available when an email or SMS channel is selected. Invocation displays the Dynamic Content Results dialog (documented separately).
§ Refresh
o Channel breakdown: this section is shown to the left, only when a multichannel offer’s results are being viewed. A proportional representation of the offer’s channel mix is shown in a pie chart.
You can hover over the pie chart to view a tooltip containing the channel name, count and percentage.
A legend is displayed below the pie chart.
For each channel, a color indicator, the channel name, count and percentage of the offer total are displayed. You can select a channel by clicking on a pie slice or legend entry. Doing so populates additional results details, which are shown to the right.
o Additional results: shown to the left of the offer Results tab when a single channel offer’s results are being viewed, and to the right of the channel breakdown pie chart when a multichannel offer is selected, this section is populated with all relevant additional results.
Each set of results – for example, as provided by a channel, or by a web analytics adapter – is contained within a category heading. Headings are displayed in alphabetical order. You can double-click a heading to roll it up or expand it as required.
Each category contains channel-specific results. Each result’s name and value are displayed.
The following categories and results are displayed in accordance with their relevance to the currently-selected channel:
§ Data Extract:
•Targeted
§ Outbound Delivery
•Targeted
•Delivery states as defined at the channel (if configured)
Note that all changes of state associated with outbound delivery offer execution are persisted in the offer history states data warehouse table.
§ Salesforce Marketing Cloud Email:
•Click Through
•Delivered (Sent – Bounces)
•Duplicates
•Forwarded
•Hard Bounce
•Invalid Addresses
•Opened
•Opened, Not Clicked Through
•Not Opened
•Other Bounce
•Sent
•Specific Link Clicks: a list of the link URLs clicked within received emails is displayed, along with the count of unique recipients who clicked the same at each. URLs are listed in descending link click count order, and up to a maximum of 100 links can be presented in this context.
•Soft Bounce
•Targeted
•Total Errors
•Unsubscribed
•SFMC Existing Unsubscribes
•SFMC Existing Undeliverables
•Forward to Social
o Facebook
o Twitter
§ SendGrid Email:
•Bounced (note that the SendGrid email server rejects email due to seemingly temporary conditions, such as a full inbox or bad email address)
•Soft Bounce (bounced/blocked; recipient will not be suppressed)
•Deferred
•Delivered
•Dropped
•Duplicates
•Opened (note that a 'True' value in the SgMachineOpen column within the SendGridEvents data warehouse table indicates that an 'Open' event was caused by a machine; 'False' indicates the event was initiated by a human)
•Opened, Not Clicked Through
•Not Opened
•Processed
•Targeted
•Unsubscribed
•Click Through
•Reported As Spam
•Invalid Addresses
•Invalid Sender Addresses
•Specific Link Clicks: please see Salesforce Marketing Cloud email for further information.
§ CheetahMail Email
•Duplicates
•Targeted
•Delivered
•Opened
•Opened, Not Clicked Through
•Not Opened
•Hard Bounce
•Soft Bounce
•Click Through
•Unsubscribed
•Specific Link Clicks: please see Salesforce Marketing Cloud email for further information.
Note that a delay of up to a day can occur prior to the availability of CheetahMail results.
§ Acoustic Email
•Click Through
•Duplicates
•Hard Bounce
•Opened
•Opened, Not Clicked Through
•Not Opened
•Opted Out
•Sent
•Soft Bounce
•Targeted
•Reply Abuse (contacts who complained through their ISP)
•Reply Change Address (replies from contacts requesting an email address change. Tracked but not acted upon)
•Reply Mail Block (messages blocked by an ISP)
•Reply Mail Restriction (the number of mail restriction replies for contacts of the domain)
•Reply Other (reply categorized as something other than one of the following: out of office reply, opt out request, abuse complaint, or change of address request)
•Suppressed
•Specific Link Clicks: please see Salesforce Marketing Cloud email for further information.
§ SparkPost Email
•Targeted
•Bounce
o Bounce reason
•Delivered
•Injection
•Spam Complaints
•Out of Band
•Policy Rejection
•Delay
•Click Through
•Open
•Initial Open
•Amp Click
•Amp Open
•Amp Initial Open
•Generation Failure
•Generation Rejection
•List Unsubscribe
•Link Unsubscribe
•Device Opened: one or more device names listed as sub-states (e.g. Chrome Windows, Firefox Linux).
§ Instiller Email
•Sent
•Processing
•Delivered
•Hard Bounce (email address does not exist or domain is unreachable)
•Soft Bounce (the message is believed to be unsolicited or the recipient mail server is throttling the number of emails allowed through)
•Returned Mail (either automated responses such as out of office replies, or an asynchronous bounce)
•Targeted
•Opened
•Click Through
•Unsubscribed
•Complaints
•Not Opened
•Opened, Not Clicked Through
•Specific Link Clicks: please see Salesforce Marketing Cloud email for further information.
§ Responsys Email
•Soft Bounce
•Hard Bounce (email address does not exist or domain is unreachable)
•Click Through
•Complaints
•Failed (no response from any of number MTAs (optionally SMTP Server Busy on Failover))
•Opened
•Sent
•Skipped (email domain or address is suppressed at the pod level, the account level, or at the campaign level; email address is invalid; missing data for $replacementField$; personalization errors, including problems with <Format Type> message or missing data for <Dynamic Values> such as Variable, Data Field, or Document)
•Unsubscribed
•Targeted
•Not Opened
•Opened, Not Clicked Through
Note that Responsys results are reported to RPI up to 6 times per day.
§ Dotdigital Email
•Soft Bounce
•Hard Bounce (email address does not exist or domain is unreachable)
•Click Through
•ISP Complaints
•Mail Blocked
•Opened
•Sent
•Delivered
•Page Viewed (need to attach Dotdigital script to public website for tracking)
•Unsubscribed
•Targeted
•Not Opened
•Opened, Not Clicked Through
§ Listrak Email
•Bounce (email address does not exist or domain is unreachable)
•Click Through
•Opened
•Sent
•Delivered
•Unsubscribed
•Targeted
•Not Opened
§ Mailchimp Email
•Click Through
•Opened
•Unsubscribed
•Soft Bounced
•Hard Bounced
•Targeted
•Not Opened
•Opened, Not Clicked Through
§ Cordial Email
•Sent
•Opened
•Click Through
•Page View
•Unsubscribed
•Bounced
•Complaint
•Targeted
•Not Opened
•Opened, Not Clicked Through
§ Luxsci Email
•Sent
•Click Through
•Specific Link Clicks
•Spam (message was marked as spam by a recipient)
•Anonymous Spam (count of Spam complaints in which the ISP of the recipient does not publish who is complaining)
•In Queue (currently in queue trying to be or waiting to be delivered)
•Soft Bounce
•Hard Fail (the message was accepted by the recipient servers successfully, but LuxSci later received a bounce back email containing a hard failure delivery status (e.g. user does not exist))
•Delivered
•Failed (permanently failed to be delivered)
•Targeted
•Not Opened
•Opened, Not Clicked Through
§ Paubox Email
•Delivered (message delivered when Secure message unchecked)
•Delivered via Secure Portal (message delivered when Secure message checked)
•Opened
•Soft Bounced
•Hard Bounced
•Targeted
•Not Opened
§ Amazon Simple Email Service (SES) Email
•Bounced
•Complaint
•Delivery
•Send
•Rejected
•Opened
•Click Through
•Targeted
•Not Opened
•Opened, Not Clicked Through
§ Amazon Pinpoint Email
•Targeted
•Sent
•Invalid Addresses
•Delivered
•Opened
•Soft Bounced (unable to be sent after a couple of re-tries)
•Hard Bounced (unable to be sent)
•Click Through
•Complaint (recipients that reported email as spam)
•Rejected (AWS determined that message contained malware and didn't attempt to send it)
•Rendering Failure (content rendering failed)
•Unsubscribe
§ Salesforce Marketing Cloud Email Data Transfer
•As Salesforce Marketing Cloud email
§ Salesforce Marketing Cloud MobileConnect SMS
•Duplicates
•Targeted
•Delivered
•Failed
§ Messente SMS:
•Duplicates
•Targeted
•Delivered
•Failed
§ Vibes SMS:
•Sent
•Failed
•Targeted
§ Salesforce.com:
•Invalid Leads
•Processed
•Targeted
•Total Errors
•Uploaded
§ Microsoft Dynamics CRM
•Disqualified
•Errors
•Open
•Processed
•Qualified
•Successes
§ Twitter Direct:
•Targeted
•Sent
§ Twilio SMS:
•Duplicates
•Targeted
•Queued
•Sending
•Sent
•Delivered
•Undelivered
•Failed
•Stop
•Stop All
•Unsubscribe
•Cancel
•End
•Quit
•Opt-Out (sum of Stop, Stop All, Unsubscribe, Cancel, End and Quit)
•Start
•Yes
•Unstop
•Opt-Back-In (sum of Start, Yes and Unstop)
•Custom Survey Response: only displayed if the offer channel's Enable survey responses field was checked. The count of how many unique survey respondents replied with a specific response, as defined by the offer's Primary and Additional keywords, is shown for each such response.
•Help (count of inbound messages with body 'HELP' sent to the Twilio number)
•Info (count of inbound messages with body ''INFO' sent to the Twilio number)
•Invalid Numbers
Note that the OfferHistory_States table's EventName column is populated for Failed and Undelivered results with '<Error Code> : <Error Message>' (as supplied by Twilio), to a maximum of 255 characters.
§ Twilio Notify Direct
•Targeted
•Sent
•Failed
§ LiveRamp
•Targeted
§ Twitter Tailored Audience
•Processed
•Success
•Targeted
§ Realtime Cache
•Targeted
•Received (the number of users received by Facebook in order to process the matching of customer data)
•Invalid entries (the number of users tagged by Facebook as invalid to use when processing the matching of customer data)
•Targeted
§ Facebook Offline Event
•Processed Entries (the number of processed entries after data was uploaded)
•Matched Entries (the number of entries determined by Facebook to have a record match)
•Valid Entries (the number of entries accepted by Facebook for match processing)
•Add Payment Info (the number of uploaded Add Payment Info events)
•Add To Cart (the number of uploaded Add To Cart events)
•Add To Wishlist (the number of uploaded Add To Wishlist events)
•Complete Registration (the number of uploaded Complete Registration events)
•Initiate Checkout (the number of uploaded Initiate Checkout events)
•Lead (the number of uploaded Lead events)
•Other (the number of uploaded events identified as Others)
•Purchase (the number of uploaded Purchase events)
•Search (the number of uploaded Search events)
•View Content (the number of uploaded View Content events)
•Contact (the number of uploaded Contact events)
•Customize Product (the number of uploaded Customize Product events)
•Donate (the number of uploaded Donate events)
•Find Location (the number of uploaded Find Location events)
•Schedule (the number of uploaded Location events)
•Start Trial (the number of uploaded Start Trial events)
•Submit Application (the number of uploaded Submit Application events)
•Subscribe (the number of uploaded Subscribe events)
•Targeted
•Invalid Event: valid Event Names are per the following list:
o ViewContent
o Search
o AddToCart
o AddToWishlist
o InitiateCheckout
o AddPaymentInfo
o Purchase
o Lead
o CompleteRegistration
o Other
o Contact
o CustomizeProduct
o Donate
o FindLocation
o Schedule
o StartTrial
o SubmitApplication
o Subscribe
§ Azure Push Direct Notification
•Targeted
•Sent
•Failed
§ Airship Push Direct
•Sends (the number of pushes sent)
•Direct (the number of direct responses to the notification)
•Targeted
§ Google Firebase Direct
•Sent
•Failed
§ Amazon Pinpoint Push
•Targeted
•Sent
•Invalid Addresses (total number of subscribers with invalid registration token/channel type)
•Undelivered
§ Google Ads Customer Match
•Received (the number of targets received by Google Ads)
•Invalid entries (the number of targets tagged by Google Ads as invalid entries)
•Targeted
§ Amazon Pinpoint SMS
•Targeted
•Sent
•Invalid Phone Numbers
•Undelivered (Targeted - Sent)
In addition, results in the following categories are displayed if appropriate:
§ Custom state flows
§ Web analytics adapters:
•Google analytics adapters: shown for channels associated with a Google Analytics adapter. Each Google Analytics metric, as defined at the web analytics adapter, is shown, along with its result. In addition, three additional metrics are provided for each goal defined at the web analytics provider. [GoalName] starts: this metric represents the number of website visitors attracted by the email offer who commenced the sales funnel. [GoalName] completions: this metric represents the number of website visitors attracted by the email offer who completed the sales funnel. [GoalName] value: a pecuniary amount, calculated as the number of completions x a (sale) value configured at the website.
Note that Google Analytics results are aggregated and anonymized…it is not possible to target further communications to specific individuals counted within Google Analytics results.
•Kissmetrics adapters: results from metrics defined at Kissmetrics adapters are displayed. One row per Kissmetrics metric is shown. Note that provision of Kissmetrics results may take several hours.
•Web Events adapters: results are collated for all web events adapters attached to a given channel. The results consist of standard web events state results, and custom web events metric and state results.
The following standard web events states are available:
o Page Visit
o Form Submission
o Link Click: a page visitor clicked on a link in the web page to which directed by an offer URL.
Custom metric results are used to show transactional values – e.g. Total Sales Amount. These are cumulative across website visitors and sessions. You can only utilize a website-provided parameter for a metric if it returns transactional data. Custom state results are used to count individuals undertaking an action at website – e.g. Made a Purchase. These are counted on an individual website visitor basis. You can respond to individual's assuming a given state in a downstream activity – for example, you might want to send an email upon a visitor’s requesting information. You can use website-provided parameter for a state irrespective of whether it returns transactional data. In both cases, results are sourced from all Web Events adapters associated with the channel.
Note also that availability of additional results is not necessarily immediate, being subject to delay while waiting for provision of data from external providers such as Salesforce Marketing Cloud and Google Analytics, and also update by the RPI Execution service. In particular, it can take several hours for Google Analytics results to be made available.
•Files tab: this provides access to any files generated if the offer supported a data extract channel, and/or if one or more audit files was/were generated. The toolbar is as the Results tab.
•Log tab: toolbar contains:
o Copy these details to the clipboard
o View Dynamic Content Results
o Refresh
•Trace tab: toolbar as Log tab.