> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Guru Digital Manager as a data source

> Bring data from Guru Digital Manager to Nekt.

Guru Digital Manager is a digital marketing and campaign management platform that helps businesses plan, execute, and track their digital marketing strategies. It provides tools for campaign optimization, performance analytics, and marketing automation to improve ROI and customer engagement.

<img height="50" src="https://mintcdn.com/nekt/0tn1_nwKYqAHn7jo/assets/logo/logo-guru%201.png?fit=max&auto=format&n=0tn1_nwKYqAHn7jo&q=85&s=53c9724a6cf904bce11c82e6c6bca86b" data-path="assets/logo/logo-guru 1.png" />

## Configuring Guru Digital Manager as a Source

In the [Sources](https://app.nekt.ai/sources) tab, click on the "add source" button located on the top right of your screen. Then, select the Guru Digital Manager option from the list of connectors.

Click **Next** and you'll be prompted to add your access.

### 1. Add account access

You will need to provide your authentication details to allow Nekt to sync your data.

The following configurations are available:

* **User token**: The user token required to authenticate against the API service. You can find the User Token on the Guru platform.
* **Start date**: Records created or updated after the start date will be extracted from the source. Format: `YYYY-MM-DD`.

Once you're done, click **Next**.

### 2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.

> Tip: The stream can be found more easily by typing its name.

Select the streams and click **Next**.

### 3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL\_TABLE. Read more about Sync Types [here](https://docs.nekt.com/get-started/core-concepts/types-of-sync).

Once you are done configuring, click **Next**.

### 4. Configure data source

Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.

To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).

Once you are ready, click **Next** to finalize the setup.

### 5. Check your new source

You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

<Warning>For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.</Warning>

# Streams and Fields

Below you'll find the available data streams from Guru Digital Manager and their corresponding fields:

<AccordionGroup>
  <Accordion title="Affiliations">
    Stream for managing affiliation data.

    | Field              | Type    | Description                                     |
    | :----------------- | :------ | :---------------------------------------------- |
    | `id`               | String  | Unique identifier                               |
    | `name`             | String  | Name of the affiliation                         |
    | `commission`       | Object  | Commission details including `type` and `value` |
    | `contact`          | Object  | Contact details including `id` and `name`       |
    | `deletable`        | Integer | Indicates if it can be deleted                  |
    | `editable`         | Integer | Indicates if it can be edited                   |
    | `is_affiliate`     | Boolean | Affiliate status                                |
    | `marketplace_id`   | String  | Marketplace identifier                          |
    | `marketplace_name` | String  | Name of the marketplace                         |
    | `product`          | Object  | Product details including `id` and `name`       |
    | `type`             | String  | Type of affiliation                             |
    | `updated_at`       | Integer | Last update timestamp                           |
  </Accordion>

  <Accordion title="Contacts">
    Stream containing contact details and information.
  </Accordion>

  <Accordion title="Subscriptions">
    Stream containing subscription data and lifecycle events.

    | Field                | Type    | Description                                                                        |
    | :------------------- | :------ | :--------------------------------------------------------------------------------- |
    | `id`                 | String  | Unique identifier                                                                  |
    | `subscription_code`  | String  | Code of the subscription                                                           |
    | `contact`            | Object  | Contact details (`doc`, `email`, `id`, `name`, `phone_local_code`, `phone_number`) |
    | `product`            | Object  | Product details (`id`, `marketplace_id`, `marketplace_name`, `name`)               |
    | `cancelled_at`       | String  | Cancellation date                                                                  |
    | `charged_every_days` | Integer | Billing cycle in days                                                              |
    | `charged_times`      | Integer | Number of times charged                                                            |
    | `contracts`          | String  | Contract details                                                                   |
    | `created_at`         | Integer | Creation timestamp                                                                 |
    | `marketplace_id`     | String  | Marketplace identifier                                                             |
    | `marketplace_name`   | String  | Name of the marketplace                                                            |
    | `next_cycle_at`      | String  | Date of next billing cycle                                                         |
    | `own_engine`         | Boolean | Indicates if using own engine                                                      |
    | `payment_method`     | String  | Payment method used                                                                |
    | `started_at`         | Integer | Start timestamp                                                                    |
    | `trial_finished_at`  | String  | Trial finish date                                                                  |
    | `trial_started_at`   | String  | Trial start date                                                                   |
    | `updated_at`         | Integer | Last update timestamp                                                              |
  </Accordion>

  <Accordion title="Transactions">
    Stream containing transaction records and tracking data.

    **Key Fields:**

    * `pptc` - Object containing detailed tracking information:
      * `tracking_group` - Object containing tracking group `id` and `name`
      * `tracking_id` - Tracking identifier
      * `tracking_name` - Tracking name
      * `tracking_type` - Type of tracking
      * `tracking_publisher` - Tracking publisher
      * `user_name` - User name
      * `checkout_id` - Checkout identifier
      * `checkout_name` - Checkout name
      * `utm_campaign` - UTM campaign
      * `utm_medium` - UTM medium
      * `utm_term` - UTM term
      * `utm_content` - UTM content
  </Accordion>
</AccordionGroup>

## Skills for agents

<Snippet file="agent-skills-intro.mdx" />

<Card title="Download Guru Digital Manager skills file" icon="wand-magic-sparkles" href="/sources/guru-digital-manager.md">
  Guru Digital Manager connector documentation as plain markdown, for use in AI agent contexts.
</Card>
