Adroll

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has state: "READY", skip to Step 2.

#### 1b. Wait for the connection to be ready

If the connection is in BUILDING state, poll until it's ready:

npx @membranehq/cli connection get  --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

The resulting state tells you what to do next:

After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get --json to check if the state moved to READY.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

| Name | Key | Description | | --- | --- | --- | | Get Ad Group Report | get-ad-group-report | Retrieves performance report data for ad groups within a date range | | Get Campaign Report | get-campaign-report | Retrieves performance report data for campaigns within a date range | | Get Ad Report | get-ad-report | Retrieves performance report data for ads within a date range | | Get Segment | get-segment | Retrieves details of a specific audience segment by its EID | | List Segments | list-segments | Lists all audience segments for a specific advertisable | | Get Ad | get-ad | Retrieves details of a specific ad by its EID | | List Ads | list-ads | Lists all ads for a specific advertisable | | Get Ad Group | get-ad-group | Retrieves details of a specific ad group by its EID | | List Ad Groups | list-ad-groups | Lists all ad groups for a specific advertisable | | Get Campaign | get-campaign | Retrieves details of a specific campaign by its EID | | List Campaigns | list-campaigns | Lists all campaigns for a specific advertisable | | Get Advertisable | get-advertisable | Retrieves details of a specific advertisable by its EID | | List Advertisables | list-advertisables | Lists all advertisables (advertising accounts) for the organization | | Get Organization | get-organization | Retrieves information about the current organization |

Running actions

membrane action run  --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run  --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the AdRoll API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

membrane request CONNECTION_ID /path/to/endpoint

Common options:

| Flag | Description | |------|-------------| | -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET | | -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" | | -d, --data | Request body (string) | | --json | Shorthand to send a JSON body and set Content-Type: application/json | | --rawData | Send the body as-is without any processing | | --query | Query-string parameter (repeatable), e.g. --query "limit=10" | | --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |

Best practices