Example: Tiffany is interested in getting the new 3rd Party Sales Attribution attached to their account to start tracking sales for WhatsApp and Apple.
Before implement bellow for WA, please check status of INC0106776
Note, you must reach out to your LivePerson Account Manager for any changes that are to be made to Houston, our backend configuration tool.
High level configuration:- To enable Houston setting for ABC and WA,
- To create Campaign for ABC and WA, with goal transaction tracking
- To create Unauthenticated Engagement for each channel - ABC and WA, and to assign skill
- Conversation is started via ABC or WA
- Agent is handling conversation and sends link to the web portal with lpTag
- Liveperson will add special query parameter to the link
- Customer goes to the link + query parameter
- Brand can attach sde to the conversation via options:
To push via lpTag:
html:
lpTag.sdes.push(
{
"type": "purchase", //MANDATORY
"total": 1, //TOTAL VALUE OF THE TRANSACTION AFTER DISCOUNT
"currency": "USD", //CURRENCY CODE
"orderId": "WEBafter", //UNIQUE ORDER ID OR RECEIPT ID
"cart":{
"products": [{
"product": {
"name": "antivirus pro plan", //PRODUCT NAME
"category": "software", //PRODUCT CATEGORY NAME
"sku": "xyz001", //PRODUCT SKU OR UNIQUE IDENTIFIER
"price": 7.8 //SINGLE PRODUCT PRICE
},
"quantity": 3 //QUANTITY OF THIS PRODUCT
}]
}
}
);
To push via API. M5NWEwZTQyZWQ3OGZkMDNj parameter comes from query of URL
Sample:
html:
curl --location --request PUT 'https://va.v.liveperson.net/api/account/24831960/app/8874e01c-6162-4b3a-ae66-5294f9de757f/report?v=1.0&vid=M5NWEwZTQyZWQ3OGZkMDNj' \
--header 'Content-Type: application/json' \
--data-raw '{"engagementAttributes": [
{
"type": "purchase",
"total": 3,
"currency": "USD",
"orderId": "monitoring after",
"cart":{
"products": [{
"product": {
"name": "antivirus pro plan",
"category": "software",
"sku": "xyz001",
"price": 7.8
},
"quantity": 3
}]
}
}
]
}'
Sample result:
- Brand’s website must have the lpTag deployed and must report engagement attributes for web visitors.
- Configure a third party connector in your account (for example: WhatsApp Connector).
- The account needs to be set up for unauthenticated messaging in order to create unauthenticated engagements. Following steps should be performed in Houston:
- Unauthenticated messaging should be enabled in AC Features - Messaging.Un_Auth_Messaging
- ACR-0 Connector creation - in order to create unauthenticated messaging connector
- The feature is enabled after creating an engagement with the connector as source.
- There is an additional toggle in Houston to control the feature, as some brands might not want the monitoring ID to be added to URLs that are shared.
See Screenshot from Houston:
Turn off “Do not add monitoring session ID to outgoing URLs” in order to enable the feature
To create a campaign, visit the campaign management UI in Conversational Cloud and select a 3rd party channel as the source.
Note: you will only see the source in the account once the feature is fully deployed.
After creating the campaign and the unauthenticated engagement, the connector will start creating a monitoring session for each consumer and automatically append the monitoring ID to all URLs that are shared by the agent/bot. This will allow the lpTag that runs on the brand’s website to continue this session and attribute all future SDEs to the consumer that started the conversation.
Once the engagement is created, all conversations that originate from the 3rd party channel will be routed to the skill of the engagement. Skill Selection will not be considered. This behavior can be changed by setting the “useSystemRouting” flag of the engagement to “true”. Currently, this is only exposed in the UI for authenticated engagements and needs to be enabled via API.
