Skip to content
Database ⇄ Marketing

Amazon DynamoDB to Rollworks integration — real-time, two-way sync

Keep Amazon DynamoDB and Rollworks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon DynamoDB and Rollworks

Give your team Rollworks's contacts, campaigns, and engagement in Amazon DynamoDB: query them with SQL, push audiences built from your own data back to Rollworks, and skip the marketing API.

Rollworks holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Amazon DynamoDB, hard to get into campaigns without manual exports.

Stacksync mirrors Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists from Rollworks into Time to Live (TTL), Tables, Items, Global secondary indexes (GSIs) in Amazon DynamoDB field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Amazon DynamoDB, from usage, orders, or account status, sync back into Rollworks to drive campaigns and ads, with Rollworks kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Use DynamoDB Streams as a change-data-capture source to push item INSERT, MODIFY, and REMOVE events into a CRM, search index, or operational database in near-real-time.
  • 02 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 03 Create and edit Prospecting v2 Campaigns and Ad Groups programmatically so budgets and targeting stay in step with an internal planning system.
  • 04 Consolidate account-level ad engagement by domain into a reporting database to join RollWorks spend against CRM Opportunities.

Common sync patterns

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Rollworks land in Amazon DynamoDB beside the matching customer record, ready for reporting and revenue attribution.

React to marketing changes as row changes

A new lead, form fill, or list change in Rollworks arrives as a row change in Amazon DynamoDB, so scoring, jobs, and notifications run in the tooling your team already uses.

Keep contact attributes consistent

Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.

What you can sync between Amazon DynamoDB and Rollworks

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Amazon DynamoDB objects Rollworks objects How this pairing syncs
Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. Items is specific to Amazon DynamoDB and Campaigns to Rollworks — each maps to any object or custom field on the other side.
Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Ad Groups and Ads to Rollworks — each maps to any object or custom field on the other side.
Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Reporting and Attribution to Rollworks — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. DynamoDB Streams is specific to Amazon DynamoDB and Target Account Lists to Rollworks — each maps to any object or custom field on the other side.
Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. Global Tables is specific to Amazon DynamoDB and Account Tiers to Rollworks — each maps to any object or custom field on the other side.
Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. Time to Live (TTL) is specific to Amazon DynamoDB and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Rollworks

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Amazon DynamoDB Rollworks Sub-second propagation

DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.

DeliveryEach detected change is written to Rollworks through its API, with automatic retries and rate-limit backoff.

Rollworks Amazon DynamoDB Interval-based propagation

DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.

DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon DynamoDB: Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.
  • Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Amazon DynamoDB ⇄ Rollworks

Connect Amazon DynamoDB and Rollworks for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Rollworks connection.

Real-time

Two-way sync

Changes in Amazon DynamoDB or Rollworks instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon DynamoDB or Rollworks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon DynamoDB or Rollworks record.

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Rollworks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Rollworks.

How the Amazon DynamoDB and Rollworks connectors work

Amazon DynamoDB

Integration surface
AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture.
Authentication
AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level.
Change detection
DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks.
Capabilities
read · write · CDC
Rate limits
Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.

Rollworks

Integration surface
REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
Authentication
OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
Change detection
Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
Capabilities
read · write
Rate limits
NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works

How to connect Amazon DynamoDB to Rollworks — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Amazon DynamoDB and Rollworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon DynamoDB connected
    Rollworks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon DynamoDB and Rollworks objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon DynamoDB ⇄ Rollworks
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon DynamoDB Rollworks
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon DynamoDB and Rollworks integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 402 integrations available for Amazon DynamoDB and Rollworks.

Popular · 5 of 402
All Amazon DynamoDB integrations All Rollworks integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own