Share
ReportHi everyone,
I'm looking for guidance on a CIJ scenario where the standard documented integration patterns don't seem to fit.
Scenario: We have a website where unknown visitors can register / sign up. The registration data needs to flow into Customer Insights – Journeys so that:
- A form submission is created in CIJ
- The standard double opt-in mechanism is triggered automatically
- No contact is created before DOI confirmation (GDPR requirement)
- After confirmation, a follow-up journey starts
Constraints:
- We cannot embed anything in the frontend of the website (no Microsoft form embed, no JavaScript snippet, no Form Capture). The API request the frontend sends, however, can be adjusted.
- We want to stay as close to Microsoft standard as possible – ideally not rebuild the DOI logic ourselves via Power Automate.
- The person is initially unknown in Dynamics – no contact / lead exists yet.
Open questions:
- Is there an officially supported, server-side way to push form submission data into CIJ from a backend system (e.g. via API gateway / middleware), so that the standard DOI mechanism kicks in?
-
The form submission endpoint exposed by published marketing forms seems to use the following pattern: https://{server}.dynamics.com/api/v1.0/orgs/{orgid}/landingpageforms/forms/{formid}.
Is this endpoint intended for backend-to-backend use, or is it strictly meant for the form capture / embedded form scenario? Is there official documentation for direct backend invocation?
- If neither path is supported: what is Microsoft's recommended pattern for "headless" registration flows that need to honor DOI before contact creation?
Any pointers to documentation, blog posts, or official guidance would be highly appreciated.
Thanks!
All responses (
Answers (
137
