Skip to main content

Customer Journey Orchestration Utility

Project description

Author: Dhivya Nagasubramanian

Purpose: The purpose of the Customer Journey Orchestration seamlessly connect and track customer interactions across multiple marketing channels, enabling businesses to gain a holistic view of each customer’s experience over time. By orchestrating touchpoints across channels, the package empowers marketers to deliver personalized, timely, and relevant messages, optimize engagement, and improve customer satisfaction and loyalty. It helps create a unified, data-driven strategy for nurturing and guiding customers through their journey, ultimately driving conversions and business growth.

Requirements packages:

NumPy - Adds support for large, multi-dimensional arrays, matrices and high-level mathematical functions to operate on these arrays.
python-dateutil - Provides powerful extensions to the standard datetime module.
dask - Dask is a flexible parallel computing library for analytics. See documentation for more information.

random - generate random numbers with in the set limits.
pandas - Dataframe utility.

Installation Instructions:

pip install journey-orchestrate

Usage Examples:

ID timestamp channel 0 1 2024-11-18 08:00:00 email
1 1 2024-11-18 09:00:00 sms
2 3 2024-11-18 10:00:00 app
3 3 2024-11-18 11:00:00 email
4 5 2024-11-18 12:00:00 sms
5 5 2024-11-18 15:00:00 direct mail

Output 1 email > sms
3 app > email
5 sms > direct mail

For a customer journey involving multiple marketing channels through which messages were delivered, we can orchestrate and stitch together the individual journey paths for each customer, providing a cohesive view of their interactions across all touchpoints.

How to use it : There are two main functions of this framework.

  1. customer_journey_orchestrate(data, ID, datetime,channel,join_string ,n_partitions) - This is the main functionionility for customer journey orchestration . 1st parameter - dataframe where the customer touch point exists.
    2nd parameter - ID on which data should be grouped.
    3rd parameter - timestamp on which we should start.
    4th parameter - column on which customer journey should be orchestrated . eg: Email, Directmail, Paid display, social media, etc.
    5th parameter - Join string. for eg: '>','|',etc. if nothing is given, default is '>'.
    6th parameter - number of partitions in which dask would operate the data for sorting.

  2. generate_random_data(1000,30,"2024-01-01", "2024-10-01",channel_lst,random_seed) - This would generate sample dataset to test the customer journey orchestrate function

    1st parameter - Number of rows to generate.
    2nd parameter - Start date.
    3rd parameter - End date.
    4th parameter - Unique Channel list : eg:['EM','SMC','PD','PS'].
    5th parameter - random_seed.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

journey_orchestrate-0.0.3.tar.gz (3.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

journey_orchestrate-0.0.3-py3-none-any.whl (4.2 kB view details)

Uploaded Python 3

File details

Details for the file journey_orchestrate-0.0.3.tar.gz.

File metadata

  • Download URL: journey_orchestrate-0.0.3.tar.gz
  • Upload date:
  • Size: 3.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.12.7

File hashes

Hashes for journey_orchestrate-0.0.3.tar.gz
Algorithm Hash digest
SHA256 18360a060ba361c5c48f3b1bf003d50a47b53d3b29d5602e8c9973134a2634ed
MD5 eeb3cbf0f1179bc3c6cc0033eaba5dc7
BLAKE2b-256 d3f0d069e11ca926662dc56ee230c797a8c9b959343a59b70b9eb4a1b3cc3940

See more details on using hashes here.

File details

Details for the file journey_orchestrate-0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for journey_orchestrate-0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 a65debf57b00ce21cd0655a8c201ae1edf101cab6338aa20262cb53b37908b52
MD5 f7e49ab73c6159e046486e716bee14ae
BLAKE2b-256 50f5131ad29963d5f9a107c03b2461d6e218baabe910c45bb4566ddcf5a588d8

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page