# Implementation Workflow

Created: 08.08.2023 

Updated: 08.08.2023 

Author: Alexander S.

Each client is assigned a dedicated solution consultant who supports the implementation from the Gravity Field side. Clients can always reach out to them with any implementation-related questions.

## 1. Kick-off Call

Once all the legal formalities are settled, we schedule a kick-off call. During this call, together with the client's product managers and developers, we go through all the implementation details and address any questions the client’s team might have. The client should have representatives from the teams responsible for working on script implementation, contexts, events, feed creation, and cookie cloning (which may involve several different teams). We strongly recommend that all call participants read through the implementation documentation in advance and come prepared.

## 2. Implementation and Feed PRDs

Based on discussions during the kick-off call and use cases for deployment (prepared in parallel by the business teams of GF and the client), we prepare:

1. Implementation PRD, which consolidates the events and implementation elements required for the initial deployment of agreed-upon use cases.
2. Feed PRD (if applicable), in which we provide recommendations for content.

{% hint style="info" %}
Please note that we may not have a full understanding of the architecture of the client's solutions, and consequently, some requirements will need to be worked out on your side.
{% endhint %}

## 3. Implementation

We recommend starting the platform deployment on a test environment.

{% hint style="warning" %}
 At this stage, it is necessary to prepare the methods required for deploying agreed-upon use cases. These methods could include:

* Adding products to the cart
* Adding products to favorites
* Opening modal windows
* Retrieving the cart contents for the current user
* Retrieving the list of favorite items for the current user
* Retrieving the list of compared items for the current user, etc. These methods may be needed for rendering and the functionality of recommendation widgets.
  {% endhint %}

## 4. Implementation Validation

To begin validating the implementation in your website/application, key elements (script, contexts, events, feed for front-end implementation, or page/choose, events, feed for API implementation) must be in place. The feed can also be validated separately as it becomes available, but validation of the website/application can only begin when all elements, including the feed, are available.

Based on the validation results, we prepare a document listing the elements that require adjustment.

As a part of the validation, we may launch a test campaign (test widget when using Gravity Field product recommendations) to ensure everything is working as expected. The validation process may go through several cycles of fixes and revalidations.

## 5. Data Validation

The final step in the process involves checking data consistency between Gravity Field and the client's trusted analytical platform (which could be Google Analytics, Yandex Metrica, or any other platform containing user count, sales count, and sales total revenue). If the data does not match, we work with the client's developers and analysts to ensure Gravity Field correctly captures all purchases and users.

{% hint style="info" %}
After a successful completion of the validation, the key point of contact for clients on the Gravity Field side transitions to the customer success manager (replacing the solution consultant).
{% endhint %}

{% hint style="info" %}
Keep in mind that during our work on personalization of your website/application, new cases regularly emerge that require various adjustments to the implementation/feed. Please plan your development team’s resources accordingly.
{% endhint %}

Technical description of implementation types: [Gravity Field Implementation Types](/lang/en/implementation/readme.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.gravityfield.ai/lang/en/implementation/implementation-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.