We are trying to integrate Adobe Analytics and Adobe Audience Manager using Server side forwarding (Configuration on Launch and analytics). We have followed the steps mentioned in https://marketing.adobe.com/resources/help/en_US/analytics/audiences/audiences.pdf . As per section "How to Verify Your Server-Side Forwarding Implementation" in document, we are able to see implementation is correct and server side forwarding is working.
We could see custom props in Analytics interface. But, when we check in AAM Signal Search (after laps of 1 day), we are not able to find any signals or custom properties.
Can you please help if there is any issues or any additional steps to be followed?
You can also utilize d_cts flag to validate the trait and segment qualification using MID,UUID or CRM ID.The flag can be enabled from backend by customer care support team.For more information on this flag,you can refer to below doc:
Just realized that, in Signal Search, we have a option where we can specify Minimum count (default value 1000), which we made it as 1 to test, results started appearing.
But, we are facing new issue that, where I have created rule based trait from Signals list view, after saving trait, trait is not showing any realizations. All values are zero. Is there something wrong?
I have created trait for the signal (c_pagename contains Bear), and hit my page multiple times manually on browser. I even ran Jmeter script to record 100 calls for same signal. Still I don't see any signals on AAM. I do see that, all response contains stuff array as empty.
What is the volume of calls required for signal to appear in Dashboard/Signal Search?
How long does this take to reflect in AAM? If this is run on scheduled basis, is there a way, we can make it appear instantly for development purpose?