Sync contacts
Create and update contacts from your backend with the attributes and consent state that your store maintains.
API · Custom integration
Connect your ecommerce store to Bitelio through the API.
For another CMS or a custom ecommerce backend, your team can connect contacts and events to Bitelio and build its own post-purchase automations. The adaptive second-purchase programme is available separately for Shopify in controlled early access.
After the first order
A journey that keeps the context.
Track meaningful events
Report events such as a first purchase or a completed delivery. Your integration determines their meaning and when to send them.
Build custom workflows
Use those events to trigger messages, delays and conditions. Your team configures the journey to match your store’s data and buying cycle.
Send from your backend
Use the sending API for transactional messages and keep secret credentials on your server.
Measure defined outcomes
Configure conversion goals from your events. Event-based revenue is gross and does not automatically reconcile refunds like Shopify orders.
Keep responsibilities clear
Your CMS remains responsible for orders, catalogue, refunds and eligibility. This integration does not provide a native store connector or the Shopify programme via API.
Getting started
What you need to get started.
Your team connects the backend and configures the journey.
- 1
Create a Bitelio project and review the custom CMS integration guide with your developer.
- 2
Define the contact attributes, consent and events your backend will provide.
- 3
Implement contact sync and event tracking using the authentication required by each endpoint.
- 4
Configure and test your workflows, sending domain, exclusions and conversion goals before enabling real sends.
Different customers. Different reasons to return.
First-order guidance
Your backend identifies the first order and reports the event that starts a helpful sequence.
A timely follow-up
Share delivery or product-use context from your store so that the workflow can wait or branch appropriately.
A defined conversion
Record a repeat-purchase event with a stable definition. Your integration remains responsible for classification and data quality.
Frequently asked questions
Is there a ready-made plugin for my CMS?
This is a custom API integration built by your team, not an automatic plugin. Shopify has its own native connection and guided programme.
Can I use the Shopify second-purchase programme via API?
No. The API route described here uses contacts, events and configurable workflows. It does not expose the Shopify guided programme or automatically sync a store’s orders and catalogue.
Do I need a developer?
Yes. Someone needs to connect your backend, manage credentials, define events and handle consent and failure cases.
Can I keep sending transactional emails?
Yes. The sending API and SMTP remain available for messages such as receipts and account notifications, alongside your configured marketing workflows.