Pull from Shopify

Shopify is an ecommerce platform for online stores and retail point-of-sale systems that consolidates shopping, payments, marketing, shipping, and customer engagement tools into a single unified experience.

Shopify is source of high quality data for both customer records and interaction records, including:

  • Complete profile data, including full names, full addresses, email address, and phone number

  • Orders, including order amounts, items and item quantities, location

  • Prices and discounts

  • Refunds and cancellations

  • Product catalog details

  • Abandoned carts

  • Customer searches

  • Guest checkout data, including email address and associated order details

This topic describes the steps that are required to pull customer profiles and orders to Amperity from Shopify:

  1. Get details

  2. Configure OAuth for Shopify

  3. Run courier

  4. Review feed and domain table

  5. Add to courier group

Get details

  1. Your Shopify Shop Name.

  2. A list of tables to be pulled to Amperity from Shopify.

Configure OAuth

OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.

Important

You must provide your Shopify shop name before you can generate the authorization link.

To configure OAuth

  1. From the Sources tab, click Add Courier. The Add Source page opens.

  2. Find, and then click the icon for Shopify. The Add Courier page opens.

  3. From the Credential drop-down, select Create a new credential. This opens the Create New Credential page.

  4. Generate an authorization link, and then visit the URL that was generated to complete the authorization process.

  5. When complete, you will be redirected to the Credentials page in Amperity.

    Verify the credential is on the page, and then return to the Sources tab.

Add courier

A courier brings data from external system to Amperity. A courier relies on a feed to know which fileset to bring to Amperity for processing.

To add a courier

  1. From the Sources tab, click Add Courier. The Add Source page opens.

  2. Find, and then click the icon for Shopify. The Add Courier page opens.

    This automatically selects shopify as the Credential Type.

  3. Select the user account you added when configuring OAuth.

  4. Select the checkbox next to the table name to pull that table to Amperity from Shopify. You may select the following tables: Customer, Customer Address, Order, Order Line, Product, and Product Variant.

  5. Click Create.

Run courier manually

Run the courier again. This time, because the load operations are present and the feeds are configured, the courier will pull data from Shopify.

To run the courier manually

  1. From the Sources tab, open the    menu for the courier with updated load operations that is configured for Shopify, and then select Run. The Run Courier dialog box opens.

  2. Select the load option, either for a specific time period or all available data. Actual data will be loaded to a domain table because the feed is configured.

  3. Click Run.

    This time the notification will return a message similar to:

    Completed in 5 minutes 12 seconds
    

Review feed and domain table

After running the Shopify courier it will create a series of feeds and domain tables. Review the records for each domain table to ensure the right data was loaded from Shopify.

Customer

The feed and domain table for customer details will contain the following fields:

  • admin_graphql_api_id

  • currency (assigned the txn/currency semantic tag)

  • created_at

  • email (assigned the email semantic tag)

  • first_name (assigned the given-name semantic tag)

  • id (assigned the ck semantic tag)

  • last_name (assigned the surname semantic tag)

  • last_order_id

  • last_order_name

  • multipass_identifier

  • note

  • orders_count

  • phone (assigned the phone semantic tag)

  • state

  • tags

  • tax_exempt

  • total_spent

  • updated_at

  • verified_email

Customer address

The feed and domain table for customer addresses will contain the following fields:

  • id

  • customer_id (assigned the ck semantic tag)

  • first_name (assigned the given-name semantic tag)

  • last_name (assigned the surname semantic tag)

  • company (assigned the company semantic tag)

  • address1 (assigned the address semantic tag)

  • address2 (assigned the address2 semantic tag)

  • city (assigned the city semantic tag)

  • province (assigned the state semantic tag)

  • country (assigned the country semantic tag)

  • zip (assigned the postal semantic tag)

  • phone (assigned the phone semantic tag)

  • province_code

  • country_code

  • country_name

  • default

Order

The feed and domain table for orders will contain the following fields:

  • admin_graphql_api_id

  • app_id

  • browser_ip

  • buyer_accepts_marketing

  • cancel_reason

  • cancelled_at

  • cart_token

  • checkout_token

  • closed_at

  • created_at

  • currency (assigned the txn/currency semantic tag)

  • current_total_discounts

  • current_total_price

  • current_subtotal_price

  • current_total_tax

  • customer_locale

  • email (assigned the email semantic tag)

  • estimated_taxes

  • financial_status

  • fulfillment_status

  • id

  • landing_site

  • location_id

  • name

  • note

  • number

  • order_number

  • phone (assigned the phone semantic tag)

  • presentment_currency

  • processed_at

  • processing_method

  • referring_site

  • source_name

  • source_identifier

  • source_url

  • subtotal_price (assigned the txn/order-subtotal semantic tag)

  • tags

  • taxes_included

  • test

  • token

  • total_discounts (assigned the txn/order-discount-amount semantic tag)

  • total_line_items_price

  • total_outstanding

  • total_price

  • total_tax (assigned the txn/order-tax-amount semantic tag)

  • total_tip_received

  • total_weight

  • updated_at

  • user_id

Order line

The feed and domain table for order lines will contain the following fields:

  • admin_graphql_api_id

  • fulfillable_quantity

  • fulfillment_service

  • fulfillment_status

  • grams

  • id

  • order_id (assigned the txn/order-id semantic tag)

  • price

  • product_id (assigned the pc/product-id semantic tag)

  • quantity

  • requires_shipping

  • sku

  • title

  • variant_id

  • variant_title

  • vendor

  • name

  • gift_card

  • taxable

  • total_discount

Product

The feed and domain table for products will contain the following fields:

  • admin_graphql_api_id

  • body_html

  • created_at

  • handle

  • id

  • product_type

  • published_at

  • published_scope

  • status

  • tags

  • template_suffix

  • title

  • updated_at

  • vendor

Product variant

The feed and domain table for product variants will contain the following fields:

  • admin_graphql_api_id

  • barcode

  • compare_at_price

  • created_at

  • fulfillment_service

  • grams

  • weight

  • weight_unit

  • id

  • inventory_item_id

  • inventory_management

  • inventory_policy

  • inventory_quantity

  • option1

  • option2

  • option3

  • position

  • price

  • product_id (assigned the pc/product-id semantic tag)

  • requires_shipping

  • sku

  • taxable

  • title

  • updated_at

Add to courier group

A courier group is a list of one (or more) couriers that are run as a group, either ad hoc or as part of an automated schedule. A courier group can be configured to act as a constraint on downstream workflows.

To add the courier to a courier group

  1. From the Sources tab, click Add Courier Group. This opens the Create Courier Group dialog box.

  2. Enter the name of the courier. For example: “Shopify”.

  3. Add a cron string to the Schedule field to define a schedule for the orchestration group.

    A schedule defines the frequency at which a courier group runs. All couriers in the same courier group run as a unit and all tasks must complete before a downstream process can be started. The schedule is defined using cron.

    Cron syntax specifies the fixed time, date, or interval at which cron will run. Each line represents a job, and is defined like this:

    ┌───────── minute (0 - 59)
    │ ┌─────────── hour (0 - 23)
    │ │ ┌───────────── day of the month (1 - 31)
    │ │ │ ┌────────────── month (1 - 12)
    │ │ │ │ ┌─────────────── day of the week (0 - 6) (Sunday to Saturday)
    │ │ │ │ │
    │ │ │ │ │
    │ │ │ │ │
    * * * * * command to execute
    

    For example, 30 8 * * * represents “run at 8:30 AM every day” and 30 8 * * 0 represents “run at 8:30 AM every Sunday”. Amperity validates your cron syntax and shows you the results. You may also use crontab guru to validate cron syntax.

  4. Set Status to Enabled

  5. Specify a time zone.

    A courier group schedule is associated with a time zone. The time zone determines the point at which an courier group’s scheduled start time begins. A time zone should be aligned with the time zone of system from which the data is being pulled.

    Note

    The time zone that is chosen for an courier group schedule should consider every downstream business processes that requires the data and also the time zone(s) in which the consumers of that data will operate.

  6. Set SLA? to False. (You can change this later after you have verified the end-to-end workflows.)

  7. Add at least one courier to the courier group. Select the name of the courier from the Courier drop-down. Click + Add Courier to add more couriers.

  8. Click Add a courier group constraint, and then select a courier group from the drop-down list.

    A wait time is a constraint placed on a courier group that defines an extended time window for data to be made available at the source location. A courier group typically runs on an automated schedule that expects customer data to be available at the source location within a defined time window. However, in some cases, the customer data may be delayed and isn’t made available within that time window.

  9. For each courier group constraint, apply any offsets.

    An offset is a constraint placed on a courier group that defines a range of time that is older than the scheduled time, within which a courier group will accept customer data as valid for the current job.

    A courier group offset is typically set to be 24 hours. For example, it’s possible for customer data to be generated with a correct file name and datestamp appended to it, but for that datestamp to represent the previous day because of the customer’s own workflow. An offset ensures that the data at the source location is recognized by the courier as the correct data source.

    Warning

    An offset affects couriers in a courier group whether or not they run on a schedule.

  10. Click Save.