When to Call Intent
Send an Intent at the journey milestones you already track, such as:- You send a prescreened offer (
lending.offer_sent) - The user signs up or logs in (
user.signed_up,user.logged_in) - The user becomes eligible for an offer (
lending.eligible_new) - The user starts an application or checkout (
lending.application_started,commerce.checkout_started)
How It Works
- Send an Intent with the event and either the user’s name plus at least one of phone, date of birth, or address, or the ID of the user’s existing Entity.
- Method acknowledges the Intent immediately. The response does not indicate whether a match occurred.
- If the user matches an individual in Method’s network, Method syncs their liabilities in the background. Recently synced or in-progress liabilities are not synced again.
- Continue your normal flow: create the Entity, collect consent, and run Connect and Updates.
Existing Entities
If the user already has an Entity, sendidentity.entity_id instead of identity.individual. Method uses the individual linked to that Entity, so no PII is required. Use this for returning users, for example on user.logged_in or lending.eligible_maintain.
Quick Start
In the Development environment, Intents are validated and stored but do not run identity matching or background syncs.
Intent API Reference
Full API documentation for Intent.