What are repurcussions of enabling AJO in datastream in Adobe Experience Platform.

Hi @shivanim ,

I'm not sure how Enabling AJO as a service in Datastream could impact numbers collected in the WebSDK dataset in AEP (assuming that you are comparing the data in AEP and CJA from the WebSDK dataset). The kind of data differences that you have mentioned could occur because of other reasons also, I'll suggest to first validate below points to make sure it is not happening simply because of how these two tools process data,

• If the CJA person ID field in your data has not populated in some purchase type records, these hits will show up in AEP but not in CJA (Assuming the field is not marked as required field in schema)
• In CJA check if you have applied any deduplication logic, based on that some orders might be getting excluded in CJA reporting while they will still show up in AEP
• Any other exclusion in CJA like segment applied on data view or report could also impact these numbers

Cheers.

Hi @shivanim 

do you even have an AJO license? I think else you won't even see it in the datastream setup.

@shivanim Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!