Clarification and Next Steps on Singular <> Adapty Integration

Hello Adapty Team,

I hope you’re doing well.

We’ve reviewed the documentation on your website regarding a Singular integration (https://adapty.io/docs/singular), but from the Singular side there is currently no active or formal integration in place. To move forward and support a working integration for shared clients, we need clarity on how this integration is intended to function, what data exchange flows are expected, and what both parties need to provide.

Specifically, we understand that Singular offers two major integration flows with partners:

1. Attribution Integration — where Singular can use tracking links and partner-provided data to attribute installs, clicks, views, etc., and send postbacks to partners for installs/events. This includes configuring tracking parameters, macros, and attribution postbacks. (https://support.singular.net/hc/en-us/articles/115002742751-Integrating-with-Singular-Attribution-FAQ-for-Partners?navigation_side_bar=true?support=true)

2. Analytics (Cost/Data Connector) Integration — where Singular pulls aggregated campaign and performance data (e.g., cost, campaign breakdowns) from a partner API or report, typically daily, to combine with attribution data and present unified analytics dashboards. (https://support.singular.net/hc/en-us/articles/360032597931-Integrating-with-Singular-Analytics-FAQ-for-Partners?navigation_side_bar=true?support=true)

Since we currently do not have any integration in place with Adapty on the Singular side, could you please help clarify the following:

1. Integration Type & Scope

• Which Singular integration flow(s) does Adapty expect to support? (Attribution, analytics data connector, or both?)

• What specific data points and events does Adapty intend to share or receive for each integration type? (e.g., installs, subscriptions, renewals, revenue, cost, campaign metadata, SKAN data, etc.)

1. Configuration & Requirements

• What setup or infrastructure is required from the Singular side to support Adapty? (e.g., tracking links, postback endpoints, credentials, credentials API, scopes)

• Is Adapty expecting server-to-server postbacks, SDK events, or hybrid integration?

• Are there any mandatory fields or macros that must be supported on both ends (e.g., campaign, publisher, creative breakdowns)?

1. Documentation & Technical Details

• Do you have technical specifications, sample payloads, API endpoints, or an example workflow of the integration?

• Are there any versioning or schema requirements we should be aware of?

1. Use Cases & Client Scenarios

• Are there current or pilot clients using this integration in production already? If so, could you share the use cases and expected outcomes?

• For recurring analytics, how often is data expected to be synced and what retention windows are supported?

1. Support & Onboarding

• Can you connect us with the technical point of contact (POC) who can explain the integration flow and implementation details in depth?

• Would it be possible to schedule a call between both technical teams to go over the integration steps, responsibilities, and timelines?

We want to ensure that we understand the expected data flows, methods, and responsibilities so both teams can support a seamless integration that benefits our shared clients.

Looking forward to your guidance and next steps.

Best regards,

Shikha Sharma | Integration Engineer | Singular