Ordergroove (Edge)

Ordergroove is a subscription management platform that helps businesses manage recurring purchases, subscription lifecycles, and billing for their online stores. It enables merchants to create and manage subscription programs, apply discounts and promotions, and support ongoing customer purchases.

Hevo uses Ordergroove’s REST APIs to replicate data from your account into the Destination of your choice. This allows you to analyze your data using analytics and reporting tools. To ingest data, you must provide Hevo with an API key to authenticate to your Ordergroove account.

Ordergroove Environments

Ordergroove provides separate environments for testing purposes and production use:

• Staging: This environment is used for pre-production testing and validation with data models that closely resemble production. A staging environment is accessed using URLs that include identifiers such as stg or staging. For example, https://rc3.stg.ordergroove.com/.

• Production: This environment is used for live business operations and contains real customer data, which is typically required for reporting and analysis. A production environment is accessed using standard Ordergroove URLs without staging identifiers. For example, https://rc3.ordergroove.com/.

Hevo supports replicating data from both staging and production environments.

---

Supported Features

---

Configure Webhooks for Capturing Delete Events

For Item and Orders objects, Hevo captures delete events through webhooks. To enable this, you must configure webhooks in your Ordergroove account using the webhook URL generated for your Pipeline. Once configured, whenever records for these objects are deleted, Hevo sets the metadata column __hevo__marked_deleted to true for the corresponding records in the Destination.

Perform the following steps to configure webhooks for capturing delete events:

1. Obtain the Webhook URL for your Pipeline

2. Create a Webhook in your Ordergroove account

Obtain the Webhook URL for your Pipeline

Perform the following steps to obtain the webhook URL generated by Hevo for your Pipeline:

1. In the Pipeline’s toolbar, click Pipeline Setup.

   

2. Scroll down to the Configure Pipeline section and copy the URL displayed in the Webhook URL field.

   

Create a Webhook in your Ordergroove account

Perform the following steps to create a webhook in your Ordergroove account to capture delete events for Item and Orders objects:

1. Log in to your Ordergroove account as a user with permission to create webhooks, such as an Account Manager Admin.

2. In the top navigation bar, hover over Developers, and then click Webhooks.

   

3. On the Webhooks page, do one of the following:

   1. If no webhooks are currently configured in your Ordergroove account, click + CREATE WEBHOOK to create one.

      

   2. If webhooks are already configured, click + CREATE to create one.

      

4. On the New Webhook page, do the following:

   

   1. In the General section, specify the following:

      • Webhook name: A unique name to identify the webhook.

      • URL: The webhook URL that you obtained from your Pipeline.

   2. In the Events section, do the following:

      • Click the expand icon next to Order events, and select the check box for order.delete event.

      • Click the expand icon next to Item events, and select the check box for item.remove event.

      Note: If you select any additional events, Ordergroove may send notifications for those events to the configured webhook URL. However, Hevo ignores these notifications, and they do not affect data ingestion.

   3. Click SAVE to create the webhook.

You can now view the newly created webhook on the Webhooks page.

---

Handling of Deletes

Ordergroove does not explicitly mark records as deleted in its REST API responses. When a record is deleted, it is no longer returned in subsequent API responses.

Hevo uses a full data refresh approach to capture delete actions for parent objects. During each Pipeline run, Hevo compares the data fetched from the Source object with the data present in the Destination table. If a record exists in the Destination but is no longer returned by the Source, the record is marked as deleted by setting the value of the metadata column __hevo__marked_deleted to True. This applies only to the following objects, for which the complete data is ingested during each sync.

• Address

• Customer

• Incentives

• Merchant Cancel Reason

• Offer Profile

• Payment

• Placement Log Responses

• Product

• Resources

For Item and Orders objects, where only new and updated records are ingested after the first Pipeline run, Hevo captures delete events through webhooks. To enable this, you must configure webhooks in your Ordergroove account. Once configured, Hevo receives a notification when records for such objects are deleted and marks them as deleted in the Destination table.

For child objects, during each sync, Hevo removes the existing data from the corresponding Destination tables and loads them with the latest data ingested from the Source. As a result, if any records are deleted for child objects, those records are not present in the Destination after the next Pipeline run.