Apphud Facebook Conversions API Python API Docs | dltHub

Build a Apphud Facebook Conversions API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Apphud provides a built-in integration to send subscription and purchase events to Meta's Conversions API for ad attribution and measurement. The REST API base URL is https://graph.facebook.com/v15.0/ and credentials are provided in the Apphud dashboard for the built-in Facebook integration.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Apphud Facebook Conversions API data in under 10 minutes.


What data can I load from Apphud Facebook Conversions API?

Here are some of the endpoints you can load from Apphud Facebook Conversions API:

ResourceEndpointMethodData selectorDescription
customers/v1/customersGETGet information about a specific user by user_id.
webhooks/webhookPOSTEvent delivery mechanism for subscription/purchase updates.
attribution/v1/attributionGET(General placeholder for Apphud API resources).
products/v1/productsGETList of available products.
subscriptions/v1/subscriptionsGETList of subscriptions.

How do I authenticate with the Apphud Facebook Conversions API API?

The integration is configured via the Apphud dashboard where you provide a Dataset ID and Access Token for Facebook's Conversions API; it does not involve calling a REST API with these credentials directly.

1. Get your credentials

To obtain your Facebook Conversions API credentials for use in Apphud, navigate to the Facebook Events Manager. 1. Select the Pixel or Dataset you wish to use. 2. Go to the Settings tab. 3. Scroll to the Conversions API section. 4. Under 'Set up manually', click 'Generate access token' to create your API access token. Ensure you have the necessary developer or administrative privileges for the Meta Business account to view this option.

2. Add them to .dlt/secrets.toml

[sources.apphud_facebook_conversions_api_source] access_token = "REPLACE_ME"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Apphud Facebook Conversions API API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python apphud_facebook_conversions_api_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline apphud_facebook_conversions_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset apphud_facebook_conversions_api_data The duckdb destination used duckdb:/apphud_facebook_conversions_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads Connections/Integrations and Events (for mapping and configuration) from the Apphud Facebook Conversions API API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def apphud_facebook_conversions_api_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graph.facebook.com/v15.0/", "auth": {"type": "api_key", "api_key": access_token, "name": "access_token", "location": "header"}, }, "resources": [ {"name": "customers", "endpoint": {"path": "v1/customers", "data_selector": "customer"}}, {"name": "webhooks", "endpoint": {"path": "webhook"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="apphud_facebook_conversions_api_pipeline", destination="duckdb", dataset_name="apphud_facebook_conversions_api_data", ) load_info = pipeline.run(apphud_facebook_conversions_api_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("apphud_facebook_conversions_api_pipeline").dataset() sessions_df = data.customers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM apphud_facebook_conversions_api_data.customers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("apphud_facebook_conversions_api_pipeline").dataset() data.customers.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Apphud Facebook Conversions API data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Apphud Facebook Conversions API?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines