The Customers resource is at the very core of the most commonly integrated use cases.
A customer may be a person or an organization.
A customer's information may be augmented using custom fields.
A customer may be tracked to lead sources (object). Rebilly keeps track of the original lead source (the introducer), the intermediary lead sources (the influencers), and the most recent lead source (the closer). Learn more about Lead Attribution here.
Customers may also be tagged, and tags can be useful for various reporting and automation tasks.
A customer may not have any orders or transactions associated, and may therefore simply be a lead.
The customers collection can be filtered by recency, frequency and monetary value for traditional marketing segmentation.
id is what makes a customer unique. Read more about how to prevent duplicate data
and maintain data quality in our article about Preventing Duplicates.
A customer may have a default payment instrument. If it does, it will be used for autopay on subscription renewals, as well as transaction requests where a specific payment instrument is not provided.
The customer does not have its own status within Rebilly.
Rebilly does track the recency (most recent paid transaction), frequency (number of transactions), and total lifetime revenue for each customer.
The customer is often referenced from other resources because many things belong to one and only one customer.
id within the Customers resource is referenced as the
within other resources.
"customerId": "<insert customer's id>"