FAQ

Frequently Asked Questions (FAQ)

This section covers the most common questions about using MadConnect — from implementation and data handling to platform support and deployment options.

1. What is MadConnect?

MadConnect is a secure data activation and movement platform that enables you to transfer data from your cloud environment (e.g., Snowflake, S3) to advertising and marketing platforms like Meta, Google Ads, and The Trade Desk.

2. What types of data workflows does MadConnect support?

MadConnect supports:

  • Audience Activation (e.g., hashed emails to Meta)

  • Conversion Syncing (e.g., offline purchases to Google)

  • Measurement & Reporting (e.g., campaign metrics into Snowflake)

3. What is a “Connection” in MadConnect?

A connection is a unique pairing of a source and a destination platform, tied to credentials and use case. For example, Snowflake → Meta Ads for audience activation = 1 connection.

4. How is MadConnect deployed?

MadConnect can be deployed in two ways:

  • Native Application: Installed in your cloud environment (e.g., Snowflake Native App)

  • API-Based: Integrated via secure REST APIs

5. Is MadConnect secure?

Yes. Data is:

  • Encrypted in transit using HTTPS

  • Never persisted post-transfer

  • Handled using least privilege access

  • Compatible with OAuth 2.0 and API key-based auth

6. Does MadConnect store data?

No. MadConnect does not retain any of your data after the transfer is complete. Transfers are logged, but payloads are not stored.

7. How do schemas work?

Each destination platform requires a specific field format. MadConnect enforces schema validation and provides standard schemas per use case. You can either conform to these or map your schema with support from our team.

8. Can I use MadConnect without code?

Yes. The UI allows you to authenticate platforms, configure connections, and initiate transfers without writing code.

9. Is there an API?

Yes. All functionality is exposed via a secure REST API, including platform setup, connector creation, and transfer initiation.

10. What platforms does MadConnect support?

Common platforms include:

  • Sources: Snowflake, S3, BigQuery, Redshift

  • Destinations: Meta Ads, Google Ads, The Trade Desk, TikTok, Amazon Ads

We are continuously adding more.

11. What happens if my connection fails?

You’ll receive error logs and detailed failure reasons in the Reports tab. Common causes include schema mismatches, expired credentials, or invalid segment IDs.

12. What level of support is included?

Every plan includes:

  • 8am–8pm EST support

  • 24/7 emergency P0 coverage

  • Onboarding and connector build prioritization

13. How is pricing structured?

You’re billed per active connection. There are:

  • Monthly Pay-As-You-Go tiers

  • Annual Credit Plans with rollover and discounts

All plans include unlimited data volume.

14. Can multiple teams use MadConnect?

Yes. Teams can create their own platform credentials and connections within the same org instance. Connections are counted per credential pair.

15. What are “credits” in the annual plan?

A credit = 1 source or destination. It takes 2 credits to form a connection. Credits can roll over and be shared across business units.

16. Can I see a list of all connectors?

Yes. The Connector Catalog in the app displays all supported platforms and use cases.

17. Can I schedule transfers?

Yes. Transfers can be scheduled based on frequency or events depending on the deployment setup.

18. What if I need a connector that doesn’t exist yet?

MadConnect supports custom connector requests. Submit your request to your rep and we will evaluate for roadmap prioritization.

19. Can I embed MadConnect into my internal tools?

Yes. With our API and flexible schema configuration, MadConnect can be embedded into internal UIs or pipelines. Some clients expose connection setup inside their data catalogs or CDPs.

Need more help? Contact [email protected]

PreviousPricing

Last updated