Summary data should not be a problem. I can see the same message, however, when I try with query service, I can see data in "interactionType" field in OOB cjm_email_tracking_experience_event_dataset. Can you double check the AJO schema field in your env:SELECT count(_experience.customerJourneyManage...

Easiest way to do this would be using query service/ data distiller, as long as you know how to differentiate between these 2 datasets, it will be quick & easy:INSERT INTO <target_dataset> SELECT * FROM <source_dataset>where <conditions>

I gave it another try, it works for me. If it is not working for you, then can you ensure that your audience contain some profiles? Sample query that run successfully for me:SELECT * FROM (SELECT array_contains(map_keys(segmentMembership['ups']), 'audienceId') as TEST_COL, workEmail.address FROM pr...

I followed the urls and I am able to access. Please ensure:The org_id is correct when you are using it from adobe ioWhen you are adding the product profiles, add everything (just to be double sure)Looking at the error, it could be an issue with "Tech account Id" as well, so try with another project ...

Is it possible to share the whole query?

To add the document link on top of @gmadala 's point, here you go: urlIn the request you have to pass the datasetId as the input parameter along with an extra query parameter as "properties" with value="observableSchema".Final url will look like: https://platform.adobe.io/data/foundation/catalog/dat...

Can you double-check the key information.Usually AEP base endpoints: platform.adobe.ioBut for Tag, the base endpoint: experience.adobe.io

Agree with you! I can see in log how the ':' is breaking apart the query. I tried with the common ones and the ascii value conversion worksAscii of semicolon: 59, henceSELECT CONCAT('Test with a semicolon ', CHR(59)) AS output;See if it helps!

You can run an quick query to get the columns:set drop_system_columns=false; SELECT to_json(_acp_system_metadata) FROM {your_table} LIMIT 1Below are the columns I can spot (I ran it for 1st time, so not sure which is what and not much help in offer from documentacp_sourceBatchIdcommitBatchIdtrackin...

There are only a few limited options you have to play around the account audience and Target is not there - please see this