AA Device data not ingested into AEP via AA Source Connector

[jlasso71]

Hi there,

I am using Adobe Analytics Source Connector to import data into Adobe Experience Platform data lake. Nevertheless, I am seeing some device data fields not populating with data - even though these fields contain data in Adobe Analytics:

• Device type
• Device model
• Device manufacturer

This also happens with "Browser name" variable.

Is this behaviour expected? Is there any method to import this data from Adobe Analytics? This is very important to us for maintaining historical data.

Thanks!

[jlasso71]

Additional details: screenshot attached show the device data I get imported.

Query:

            SELECT device
            FROM tableXXX_midvalues

Example result:

 

[Elanchezhiyan_E]

Hi jLasso,

If you're using the standard schema mapping in the Adobe Analytics Source connector, you can customize your schema based on your Adobe Analytics data by creating a custom field group—for example, to capture user agent details.

Within the Source connector, you can also perform custom mappings by manually mapping values into these custom field groups. Additionally, you have the flexibility to use functions, fields, and operators when creating calculated fields.

For more details, refer to the documentation: https://experienceleague.adobe.com/en/docs/platform-learn/tutorials/sources/ingest-data-from-adobe-a...

Good Luck..!

Thanks

[GigiCotruta]

Hi, @jlasso71 , 

Could you give us more details on the schema and mapping that you have used

[jlasso71]

Hi @Elanchezhiyan_E @GigiCotruta ,

At this point, I am just using Standard mappings, since I was assuming AA device data (device.model, device.type, device.manufacturer) was populated automatically. The schema I am using contains "Adobe Analytics Experience Event" and "AEP Web SDK Experience Event" field groups (Adobe-provided).

According to your comment @Elanchezhiyan_E , these fields need to be manually mapped into custom field groups?

Thanks!

[GigiCotruta]

Indeed, @jlasso71

Try to map these fields and let us know if that solved your problem.

Basically, the connector maps some default fields. Some clients do not need device info, therefore, I assume that might have been the reason why it is not automatically mapped. 

[John_Man]

Hi @jlasso71 

In your CJA data view, e.g. device type, do you see below schema fields?

_globallookupscjaapac.deviceType

device.type

Since my implementation have both AA connector and Web SDK, I forgot which field is populated by connector or SDK, but I believe it should be available out of the box in the AA connector, as I merged them with a Derived Field and there is no custom mapping in my AA connector config for device type.

Hope it helps.

Thanks,

John

[jlasso71]

Hi @John_Man ,

That's very interesting, I also have a mixed implementation (AA connector for historical data, Web SDK for new data) and I indeed have an Adobe lookup in CJA with Device type.

How did you configure a derived field "Device type" to combine both sources?

Thanks!

 

[John_Man]

Hi @jlasso71 

Use the Merge function, see below.

Thanks,

John

[jlasso71]

Hi @John_Man ,

Let's see if I have understood it correctly:

Final Output - Merge

• Value 1: Device Type - Rule 1 (Lookup). This assigns a Device Type value based on "Type identifier", a Lookup ID coming from device.typeid via AA source connector. 
• Value 2: Type. This is the device.type field coming from Adobe WebSDK.

I will let you know as soon as I have tested it.

Best regards,

[John_Man]

Hi @jlasso71 

That's right, and hope it works well.

You may have to merge some other fields with simialr situation where differnet schema fields are used in connector and SDK. And some of them could be more challenging as their lookup values are different e.g. Device Name, Province Name.

Thanks,

John