This page provides FAQs and troubleshooting information for common issues related to Customer Data Platform (CDP).
A360
)Tracker
)The abandoned cart model includes all the products added to a customer’s cart after the most recent transaction.
Abandoned cart campaigns should be built using the following criteria: “INCLUDE (Abandoned a cart <in the timeframe you need>); EXCLUDE (Placed a transaction <in the same timeframe> OR Performed an event <checkout> <in the same timeframe>)”.
Use this criteria to avoid missing use cases where a mastercustomer has N child contacts and abandoned a product in one child contact. However, another child contact bought it later, either online or offline.
This issue occurs due to the following reasons:
Workaround:
This issue occurs if the connector is not published.
Workaround:
Unpublished
, click
the corresponding connector and publish it.This issue occurs when the backend service is down.
Workaround:
This issue occurs due to the following reasons:
Workaround:
A360
)¶This issue occurs when the A360
role name is not present.
Workaround:
This issue occurs when the bearer token expires.
Workaround:
This issue occurs when the URL has a missing searchterm.
Workaround:
?searchTerm=
in the host API URL.Tracker
)¶This issue occurs when the Tracker
role name is not present.
Workaround:
This issue occurs when incorrect or incomplete payload data is sent to the Tracker API.
Workaround:
Send the payload data with the correct format and all the mandatory fields. For example,
{
"transactionitems": [],
"transactions": [],
"customers": [],
"events": []
}
This issue occurs when you use invalid AWS credentials for provisioning.
Workaround:
This issue occurs due to the following reasons:
Workaround:
This issue occurs due to the following reasons:
Workaround:
Owing to security reasons, CDP cannot display the credentials more than once. You must save the credential information when they are generated. If you do not have access to your old credentials and want to access the instance, you must regenerate credentials and use the new set of credentials for accessing the instance.
CDP allows you to create a batch with no more than 200 records. If you attempt to create a batch that exceeds the limit of 200 records, the system displays an error message. For example,
The request is over the 200 batch limit. Remove profiles to Submit Request.
Workaround:
To ensure that you do not cross the 200 limit, remove the records. You can create separate batches with each batch containing a maximum of 200 record.
Campaign execution in CDP fails with a zero audience warning message. You can view the warning message on the Campaign History page of each campaign. You can get zero-audience count in CDP campaigns due to the following reasons:
You are unable to view the Attribution section in the Metrics tab as the multi-touch attribution feature is not provisioned for your account.
To get access to this feature, contact your Acquia CSM or AM.
This issue occurs when: