Issue¶

Personalized slot is not visible in Experience Builder on the following x and y pages.¶

Resolution¶

To identify whether Slot "A" was actually defined for a particular page, perform the following steps:

• Navigate to the page in question and open up the browser "inspector" tool.
• Navigate to the Network tab and reload Experience Builder, if you have it open in administrative mode. Make sure your Network tab is filtered to All or XHR. 
• Look for a slots?account_id=...GET request. There will be an Options and a GET request.
• Click on the GET request, and click Preview which will display a list of slots. This list is what is being returned by the Lift API.

We are working on more extensive product documentation on how to use various tools to query the Lift API to get a list of all slots created on a site.

For now, you can reference Using the Acquia Lift APIs, specifically the section on Testing your API implementations which uses the tool Postman .

General steps:

1. Set up Postman for Decision API following the documentation in Github: https://github.com/acquia/http-hmac-postman.
2. Set up the Postman call for the slots endpoint of Decision API: http://docs.lift.acquia.com/decision/. Here is an example of a slot API endpoint: https://us.perz-api.cloudservices.acquia.io/slots?site_id=example1&account_id=EXAMPLE2.
3. Add parameters of what slots you want to locate, example by site.

Once you have determined, the original page that a slot was defined on, go ahead and add/define the other page paths that the slot should appear on via the Configure tab, and add the page paths to the Slot Pages field as explained in Creating slots in Experience Builder.

Cause¶

The "miing" slot was not actually defined on the pages previously aumed.