Act-On Reader

Note

This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.

Act-On facilitates the design and management of automated marketing campaigns across a variety of platforms, including email, social media, and landing sites, in order to cultivate leads, encourage interest, and monitor and evaluate campaign performance using the platform's comprehensive analytics. Striim's Act-On Reader extracts data from the application and migrates it to other enterprise apps or data warehouses, enabling teams to combine ad performance data with other business-critical information.

Feature summary

Feature		Supported?	Notes
Objects	Standard objects	✓
Objects	Custom objects	✓
Authentication	Basic authentication		Username and password
	OAuth authentication	✓	Manual configuration based
	Custom authentication methods		Not all methods may be supported
Operations	Automated mode	✓
	Initial load	✓
	Pull-based incremental load	✓
	Push-based incremental load
	Automated pipeline
Governance	Connection profile
	Sherlock AI
	Sentinel AI
Schema handling	Initial schema creation	✓	Works with supported targets
Schema handling	Schema evolution
Setup	Wizard template
	Flow Designer	✓
	Striim TQL	✓
Runtime	Resilience/recovery	✓
	Parallel execution
	Metrics	✓	Standard metrics

Supported authentication method

The Act-On Reader supports OAuth authentication. Creating a connection requires registering an account on Act-On, sending a request to Act-On's authorization endpoint to obtain an authorization code, using the authorization code to request an access token and refresh token, and setting the Striim connection properties.

To create a connection using OAuth authentication:

Sign up at https://developer.act-on.com/provision/. You will get an email with the Client ID and Client secret.
Set the Redirect URI to a page on your website where you would like the user to be returned after the user grants permission to your app.

Send a request to Act-On’s authorization endpoint, including your client ID, redirect URI, and requested scopes. For example:

https://auth.actonsoftware.com/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_REDIRECT_URI
&response_type=code&scope=read

Once authenticated and authorized, Act-On redirects to the specified redirect URI with an authorization code appended as a query parameter:
```
YOUR_REDIRECT_URI?code=AUTHORIZATION_CODE
```

Use the authorization code received in the redirect to request the access token and refresh token by sending a POST request to the Act-On token endpoint:

POST https://auth.actonsoftware.com/oauth/token
Content-Type: application/x-www-form-urlencoded

The request body must contain:

client_id=YOUR_CLIENT_ID
client_secret=YOUR_CLIENT_SECRET
code=AUTHORIZATION_CODE
redirect_uri=YOUR_REDIRECT_URI
grant_type=authorization_code

If the request is successful, you will receive a response containing the access token and refresh token:

{
  "access_token": "ACCESS_TOKEN",
  "refresh_token": "REFRESH_TOKEN",
  "expires_in": 3600,
  "token_type": "bearer"
}

Supported objects

The following are the supported objects for reading from Act-On:

Campaigns
Categories
DrilldownReports
Hardbounce
Images
List_MyList
Media
Messages
Optout
OtherLists
Programs
Reports
ReportsByPeriod
ScoreDetails
Spamcomplaint
SubscriptionOptOuts
Users

Act-On Reader properties

Property	Type	Default value	Notes
Client ID	String		The client ID assigned when you register your application with an OAuth authorization server.
Client secret	Password		The client secret assigned when you register your application with an OAuth authorization server.
Access token	Password		The access token for connecting using OAuth, which is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.
Refresh token	Password		The OAuth refresh token for the corresponding OAuth access token.
Connection pool size	Integer	20	Specifies the maximum number of active connections.
Exclude tables	String		A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors.
Incremental load marker	String		The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval. Specify the name of the column that contains the start position value. This column must meet the following criteria: It should have an integer or timestamp data type (for example, a creation timestamp or an employee ID). The values must be unique and continuously increasing to ensure proper incremental reading.
Migrate schema	Boolean	False	Only available in Initial Load or Automated mode. Set to `True` to enable initial schema migration, which propagates the object schema from the source to the target.
Mode	Select list: Automated mode Initial load Incremental load	Automated	Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load.
Polling interval	Integer	5m	Specifies an interval as an integer followed by a unit. Supported units are days (`d`), hours (`h`), minutes (`m`), or seconds (`s`). The reader polls the source at the specified interval.
Start Position	String	%=-1	Value of the incremental load marker that defines the initial reading position.
Tables	String		A semicolon-delimited (;) list of objects to read from the source. Supports the `%` wildcard. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. Do not modify this property when recovery is enabled for the application.
Thread pool count	Integer	10	The number of parallel running threads. The default value of zero specifies single-threaded operation. When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice.