> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/growave.md).

# Growave

Reward customers with Growave loyalty points, discounts or store credit when they complete a Zigpoll survey, using Shopify Flow.

[Growave](https://growave.io/) is a loyalty and rewards app for Shopify: points, VIP tiers, referrals, reviews and wishlists. Connected to Zigpoll through Shopify Flow, it rewards customers for answering a survey. A shopper who finishes your post-purchase survey gets points or a discount, and you get more responses.

Nothing needs to be turned on in Zigpoll. The connection is one Shopify Flow workflow and one earning rule in Growave.

## How it works

1. A customer answers your survey. Zigpoll fires the **Zigpoll Survey Completed (with email capture)** trigger in [Shopify Flow](https://docs.zigpoll.com/shopify-app/shopify-flow.md), which carries the Shopify customer.
2. The workflow sets a true/false metafield on that customer, for example `custom.zigpoll_survey_completed`.
3. Growave watches that metafield with its **Customer metafield** earning action and issues the reward when the value becomes true.

## What you need

* Zigpoll installed on your Shopify store.
* Shopify Flow.
* A Growave plan that includes the **Customer metafield** earning action. At the time of writing that is Growth or higher; check [Growave's guide](https://help.growave.io/en/articles/18360227-integrating-growave-with-zigpoll-customer-surveys) for the current requirement.

## Setup

#### Step #1: Create the customer metafield in Shopify

1. In your Shopify admin, go to **Settings → Metafields and metaobjects → Customers**.
2. Click **Add definition**.
3. Name it (for example **Zigpoll survey completed**) and note the namespace and key, for example `custom.zigpoll_survey_completed`.
4. Choose the type **True or false**.
5. Click **Save**.

#### Step #2: Add the earning action in Growave

1. In Growave, go to **Rewards → Points → Ways to earn**.
2. Click **Add ways to earn** and choose **Customer metafield**.
3. Pick the reward and its amount.
4. Enter the namespace and key from Step #1.
5. Set the value type to **Boolean**, the condition to **Equals** and the value to **True**.
6. Give it the title your customers will see (for example **Complete our survey**) and click **Save**.

#### Step #3: Build the workflow in Shopify Flow

First copy the ID of the survey you want to reward. In Zigpoll, open the survey and go to **Settings → General → Details → Survey ID**.

1. In your Shopify admin, open **Apps → Flow** and click **Create workflow**.
2. Click **Select a trigger**, search for Zigpoll and choose **Zigpoll Survey Completed (with email capture)**.
3. Add a **Condition**: **Survey → ID** is **Equal to** your Survey ID. Without it, every Zigpoll survey on your store earns the reward.
4. Under **Then**, add the action **Update customer metafield**. Choose the customer from the trigger, select your metafield and set the value to `true`.
5. Name the workflow and click **Turn on workflow**.

#### Step #4: Test it

1. Answer the survey as a test customer.
2. Wait a few minutes. Zigpoll fires Flow triggers about a minute after the last question, and post-purchase surveys also wait for Shopify to finish processing the order.
3. In Shopify, open the customer and check that the metafield is **True**.
4. In Growave, open the same customer under **Rewards → Customers** and check that the reward appears in their activity.

## Good to know

* **The customer must be known.** The trigger only fires when the response is tied to a Shopify customer: a post-purchase survey, a logged-in shopper, or a survey that asks for an email address. Anonymous on-site responses earn nothing. See ["with email capture" never fires](https://docs.zigpoll.com/shopify-app/shopify-flow.md#with-email-capture-never-fires).
* **The reward is not instant.** It arrives a minute or more after the last answer, so avoid promising "instant" points in your survey copy.
* **Partial responses fire the trigger too.** Someone who answers the first question and leaves still sets the metafield, about 10 minutes later. To reward only finished surveys, add a second condition in the workflow that checks the **Responses** list for the handle of your final question.
* **One reward per customer.** The metafield stays true once set, so a customer who answers again does not earn twice.
* **Tell shoppers about it.** Mention the reward in the survey's opening question or on your Growave loyalty page. An incentive nobody knows about does not lift response rates.

If the workflow does not run, see [My Flow isn't running](https://docs.zigpoll.com/shopify-app/shopify-flow.md#my-flow-isnt-running).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/integrations/growave.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
