Skip to content

Integrations

Approved images land in live campaigns. No exports, no re-uploads.

GetPhoto ships directly into Shopify, Amazon, Meta, Klaviyo, TikTok, and Google Ads. Once a brief is approved, the winning asset syncs to your storefront or ad set — typically within four minutes.

Connect your store See the workflow

How each connection actually works

Six direct integrations, each documented as a workflow.

An integration is a sync trigger and a permission scope — not a marketing badge. Below is exactly what happens when an asset is marked approved in GetPhoto, the trigger that pushes it to the destination, and the expected latency operations leads should plan against.

  1. 01

    Shopify

    Storefront sync

    Setup steps

    1. Install the GetPhoto app from the Shopify App Store.
    2. Approve the read-only product catalog scope and the write scope for product media.
    3. Pick a default destination: product page hero, collection thumbnail, or both.
    4. Choose whether to auto-approve any asset or route to a human reviewer.

    Sync behavior

    Trigger: asset status changes to Approved in the GetPhoto dashboard. The approved file replaces the product's primary image (or appends to the gallery, per your routing rule) inside the same Shopify transaction. Variant-level images route by SKU.

    Expected latency
    ~3 minutes end-to-end
    Direction
    GetPhoto → Shopify (one-way)
    Auth model
    OAuth 2.0, scoped to store
  2. 02

    Amazon Seller Central

    Marketplace sync

    Setup steps

    1. Generate a SP-API role in Seller Central with Product Image upload scope.
    2. Paste the role ARN into the GetPhoto integrations panel.
    3. Map each GetPhoto project to a marketplace (US, EU, JP) and ASIN.
    4. Confirm the main image meets Amazon's 100% fill requirement before activation.

    Sync behavior

    Trigger: asset status changes to Approved. The approved file uploads to the mapped ASIN's main or alternate slot through SP-API. Files are normalized to Amazon's required dimensions and color profile automatically before upload.

    Expected latency
    ~6 minutes end-to-end
    Direction
    GetPhoto → Amazon SP-API (one-way)
    Auth model
    SP-API role ARN, scoped per marketplace
  3. 03

    Meta Ads Manager

    Ad account sync

    Setup steps

    1. Connect a Facebook Ad Account via OAuth from the GetPhoto dashboard.
    2. Select the target ad account and the default page for asset association.
    3. Pick the sync destination: a single live campaign, a creative library folder, or both.
    4. Set a label rule (e.g. tag approved assets with the brief ID) for downstream filtering.

    Sync behavior

    Trigger: asset status changes to Approved. The approved file uploads to the Marketing API as an image asset and attaches to the chosen campaign's creative, with optional dynamic ad support. Files publish at the ad's preview status — not live — until the campaign owner flips the toggle.

    Expected latency
    ~4 minutes end-to-end
    Direction
    GetPhoto → Meta Marketing API (one-way)
    Auth model
    Facebook OAuth, ad-account scoped
  4. 04

    Klaviyo

    Lifecycle sync

    Setup steps

    1. Generate a Klaviyo private API key with image-write scope.
    2. Paste the key into the GetPhoto integrations panel and select the account.
    3. Map each GetPhoto project to a Klaviyo flow or template.
    4. Choose auto-approve or human review before image insertion.

    Sync behavior

    Trigger: asset status changes to Approved. The approved file uploads to Klaviyo's image library and swaps into the mapped email or SMS template's hero block. Versioned so prior sends retain their original asset.

    Expected latency
    ~2 minutes end-to-end
    Direction
    GetPhoto → Klaviyo (one-way)
    Auth model
    Private API key, account scoped

Two additional integrations — TikTok Ads and Google Ads — follow the same trigger model (asset status → destination) with the same one-way sync latency band. Setup steps and SP-API / OAuth scopes are documented in the GetPhoto help center.

Time to live campaign

What an integration actually replaces.

The integration pitch is rarely about features — it's about the hours lost between "asset approved" and "asset in front of an audience." Below is the path operations leads defend in their budget meeting.

Path A

Manual export + DAM + agency re-upload

The status quo for most DTC teams before they evaluate a sync tool.

  1. Designer exports approved asset from photo tool~12 min
  2. Drops file into shared DAM, notifies reviewer~25 min
  3. Agency or in-house marketer downloads, renames, resizes per channel spec~45 min
  4. Manual upload to Shopify product page, Meta ad set, Klaviyo template~35 min
  5. QA: pixel dimensions, color profile, copy alignment~20 min
  6. Campaign goes live~2h 17min median

Variable per team. Measured against a 12-asset campaign at a typical 4-person DTC operation.

Path B

GetPhoto direct sync

Approved asset triggers a write to every connected destination in parallel.

  1. Asset status changes to Approved in GetPhoto0 min
  2. Shopify, Amazon, Meta, Klaviyo each receive a parallel write~3 min
  3. QA is performed by GetPhoto's pre-upload checks (size, color profile, channel spec)included
  4. Assets land as drafts in Meta Ads, live in Shopify, attached in Klaviyo templates~4 min
  5. Marketer flips the campaign from draft to live in Meta1 click
  6. Campaign goes live~4m 12s median, measured in 2024

Median sync latency across 12,400 orders fulfilled in 2024. Excludes the marketer's final approval click in Meta.

A laptop dashboard showing time-to-live-campaign metrics, photographed editorial-style on a warm off-white desk.
FIG. 01 · Time-to-live-campaign across 12,400 GetPhoto orders fulfilled in 2024, segmented by sync path.

Procurement checklist

The four questions your IT reviewer will ask, answered on this page.

Operations leads rarely get blocked on feature parity — they get blocked on the procurement gate. These are the four answers we publish up front.

SOC 2 Type II

Certified since November 2023

Annual audit with a Big Four firm. Report available under NDA from the GetPhoto trust portal. Covers availability, confidentiality, and processing integrity.

Trust portal: /customers/

Permission scoping

Read where we can, write only where we must

Each integration requests the minimum OAuth scope required for sync: read-only product catalog on Shopify, image-write only on Amazon SP-API, ad-account-scoped on Meta. No admin scope is requested by default.

Scope matrix: /customers/

Approval workflow

Human-in-the-loop by default

Auto-approve is opt-in per project. The default routing sends every approved asset to a designated human reviewer in the GetPhoto dashboard before the sync trigger fires. Reviewer identity is logged per asset.

Audit log retention: 24 months.

Audit trail

Every sync is a logged event

Each sync writes a row to an immutable event log: asset ID, integration, destination, timestamp, reviewer, and confirmation token from the destination platform. Exportable as CSV or pushed to your SIEM via webhook.

Webhook destination available on request.

Procurement-stage questions

What operations leads ask before approving a new stack vendor.

Do you support SSO and SCIM provisioning?
Yes. GetPhoto supports SAML 2.0 SSO with Okta, Azure AD, and Google Workspace. SCIM 2.0 provisioning is available on Business and Enterprise plans and deactivates a GetPhoto seat within five minutes of an IdP-side removal.
Can we trial the integrations on a sandbox account?
Yes. A 14-day sandbox is available on request — connects to a Shopify development store, a Meta test ad account, and a Klaviyo sandbox account, with a pre-seeded brief that mirrors a real product photo workflow. Sandbox activity is isolated from production data.
Where is data stored, and can we pin it to a region?
Asset files and metadata are stored on AWS in us-east-1 by default. EU and APAC residency are available on Enterprise plans — files at rest remain in the selected region, and cross-region replication is disabled by default for compliance reasons.
What happens if a sync breaks mid-campaign?
Every integration includes a 24-hour broken-sync recovery. If a destination rejects an asset (dimension mismatch, expired OAuth token, rate-limit), GetPhoto queues the asset for automatic retry and surfaces the failure in the dashboard with a one-click replay button. 94% of surveyed customers cited the 100% reshoot guarantee and unlimited revisions as the reason they switched from competitors — the same SLA covers sync-side failures.

Pricing is unchanged by integrations — flat $9 per asset, no per-connector fee. SSO, SCIM, and EU/APAC residency are the only line items that vary by plan.

Connect your store

One authorization click. Watch the first approved image sync into a live campaign before lunch.

The fastest way to evaluate GetPhoto is to connect a real store, submit a brief, and watch an approved asset land in your Shopify product page and your Meta ad set without a manual export in sight.

Connect your store Talk to an integrations specialist

First photo is free on every new account. No credit card required to start. Cancel an integration at any time from the dashboard — no sales call required.