is there a built-in integration between AEM Forms and the AEP (dataset) to report on these forms in CJA?
I'm not only referring to the forms views and forms submitted, which should be relatively easy to track with the Web SDK, but also reporting on the form questions and responses.
Thank you!
Solved! Go to Solution.
Views
Replies
Total Likes
@Olivier_Blonste At present with my experience there is no such built-in integration at this movement, but we can design this in few ways based on your need.
WebSDK (Near Real Time)
1) This approach best fit for solutions where you have use cases to consume this in future for audience(Edge perse), event forwarding scenarios and availability of data in profile in near real time situations, however you can also send data via this approach without considering above use cases.
Streaming Ingestion (Near Real Time)
1) This approach best fit for solutions where you have use cases to consume this in future for audience(streaming pers) and availability of data in profile in near real time, however you can also send data via this approach without considering above use cases.
Batch Ingestion
1) This approach you can persist this data elsewhere and ingest as batch files for processing and helps audience (batch perse).
Common Considerations for all three approach
1) Ingest these kind of data to a new custom Experience Event Schema/Dataset (leverage Dataset overwrite functionality for websdk and streaming implementations) to have clean separation.
2) Additionally you can also not enable the aforementioned dataset if you planning to just consume with CJA, with this you are also not consuming profile richness entitlement ( Total data Volume new metric for the same) and Addressable Audience entitlement.
Let me know if you more details on this.
~cheers,
NN.
@Olivier_Blonste At present with my experience there is no such built-in integration at this movement, but we can design this in few ways based on your need.
WebSDK (Near Real Time)
1) This approach best fit for solutions where you have use cases to consume this in future for audience(Edge perse), event forwarding scenarios and availability of data in profile in near real time situations, however you can also send data via this approach without considering above use cases.
Streaming Ingestion (Near Real Time)
1) This approach best fit for solutions where you have use cases to consume this in future for audience(streaming pers) and availability of data in profile in near real time, however you can also send data via this approach without considering above use cases.
Batch Ingestion
1) This approach you can persist this data elsewhere and ingest as batch files for processing and helps audience (batch perse).
Common Considerations for all three approach
1) Ingest these kind of data to a new custom Experience Event Schema/Dataset (leverage Dataset overwrite functionality for websdk and streaming implementations) to have clean separation.
2) Additionally you can also not enable the aforementioned dataset if you planning to just consume with CJA, with this you are also not consuming profile richness entitlement ( Total data Volume new metric for the same) and Addressable Audience entitlement.
Let me know if you more details on this.
~cheers,
NN.
Thank you, NN!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies