Integrations and source ownership

• email-send service. Connect rendered message handoffs, inbound engagement activity and unsubscribe requests. Agree sender identity, the service’s sending acknowledgement and how suppression confirmation is reconciled with the local request.
• crm-leads. Connect the lead profile feed and qualification writeback. Preserve lead identity across score and qualification changes, then check the acknowledged result and the owner responsible for follow-up.
• Forms and CMS. Map form fills, page visits and content downloads with source time and known lead identity. Preserve the form code, content title, page address and original payload where the source provides them.
• webinar platform. Keep registration and attendance distinct. Correlate the signal to the intended lead and journey before using attendance as scoring or goal evidence.
• program webhook target. Agree the receiving system for a webhook action and inspect its response against the affected member and step.

Marketing Systems Admin coordinates access through the customer’s normal setup process. Marketing Manager agrees the business meaning of each signal and acknowledgement. Marketing Operations tests identity mapping and reviews the operating result. Assign an owner to unmatched input and keep source credentials outside authored content.

Rehearse a known lead, an unmatched identifier, repeated input, a provider timeout and revoked access before opening a larger feed. Preserve the source payload for investigation. Reconcile accepted, rejected and pending work to the originating lead, then review the result with the operator. Keep the manager’s content decision, the member’s execution history and the receiving service’s response available for the same case.

Use the implementation plan.