Testing Your SDK Integration

After you have integrated the Salesforce DMP SDK into your app, check the following to ensure data collection and usage functions properly before publishing to your users.

With a device simulator or viewing requests via a network proxy (such as the Charles Proxy), check the following after building your app with Salesforce DMP.

      1. config load

        This is the request on SDK initialization at app open.
        http://cdn.krxd.net/controltag/config/<APP CONFIG ID>?mobile=1
      2. Optout check

        This checks if the device ID has been opted out of Salesforce DMP tracking through DAA's AppChoices. If so, an "optout" ID will be sent for that device to Salesforce DMP, therefore not making it identifiable.
        https://cdn.krxd.net/userdata/optout/status?users=
      3. userdata

        This returns the users segments to the app for usage. There is a 20 minute cache per request, therefore do not expect to see it on every load.

        For new integrations, its is expected to not be part of segments. This is because segments have either not been created, or the device has not been processed to be associated to segments.
        http://cdn.krxd.net/userdata/get?_kpid=<ACCOUNT ID>&_kuid=<IDFA/ADID>
      4. pixel.gif

        This is the request when calling trackPageView. It includes a set of default device and configuration information. More importantly, all user data in the parameters &kua<name> (user attribute) and &kpa<name> (page attribute). Be sure to check that the attribute names and values match the specified data plan.
        http://beacon.krxd.net/pixel.gif?...
      5. event.gif (if used)

        This is the fireEvent request. Ensure the event uid is included and any event attributes are part of the request. 
        http://beacon.krxd.net/event.gif?event_uid=<EVENT ID>&...
      6. Google DFP integration (if DFP custom key targeting is used)

        For DFP specifically, look for a request to g.doubleclick.net. Check for the Salesforce DMP segments to be passed in the &cust_param as this key-value: ksg=<SEGMENT IDs>

 

    1. transaction.gif (if used) This request is sent after a purchase is made to capture price, quantity by order date. 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.