Specter + Dotdigital
Everything you need to connect Specter and Dotdigital: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 20 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 5-15 minutes once the credentials have been issued
Prepare Specter
- Confirm the correct environment
- Request the credentials from the responsible party
- Receive the credentials securely
- Paste the values into Junipeer
- Run a connection test
- about 5 minutes
Prepare Dotdigital
- Open API users in Dotdigital
- Create a new API user
- Leave the generated username unchanged
- Set the password and enable the user
- Save and copy the credentials
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
Junipeer - Customers
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Specter (50)
| Setting | What it controls | Key |
|---|---|---|
| API User Id | Enter the API user ID that Junipeer should use to connect. | api_user_id |
| API User Key | Enter the API user key that belongs to the API User Id . | api_user_key |
| Add Payment Reference Prefix | Add a prefix in front of every payment reference sent to Specter. | specter_payment_reference_prefix |
| Add Variant Types | Add the variant types used to create variants in Specter, so variants are imported correctly. | specter_variant_types |
| Always send shipping row | Decide whether orders sent to Specter should always get a shipping row. | specter_always_send_shipping_row |
| Currencies (key, title) | List the currencies you use in Specter, so they can be chosen in other Specter settings. | specter_available_values_currencies |
| Custom fields to map from Shopify attributes | Choose which Shopify attribute fills each custom or extra field on the article in Specter. | specter_custom_fields_map |
| Default (Shipping fee) Article number | Enter the article number (SKU) used for the shipping fee on order rows in Specter. | specter_default_shipment_article_no |
Show all 50 settings
| Setting | What it controls | Key |
|---|---|---|
| Default Currency Code | Choose the default currency for articles. | specter_default_currency_code |
| Default Discount Article number | Enter the article number (SKU) used for discounts on order rows in Specter. | specter_default_discount_article_no |
| Default Specter Warehouse ID | Enter the ID of the Specter warehouse to use as the default for stock. | specter_default_stock |
| Discount Percentage | By default, Junipeer sets both the price and the discount percentage on each order row in Specter, when the order has them. | specter_discount_percentage |
| Discount Price Lists (Rabattprislistor) | List the discount price lists (rabattprislistor) you have in Specter, so they can be chosen in other Specter settings. | specter_available_values_price_lists |
| Exclude Orders created before this date | Orders created in Specter before the date you choose here are not synced. | stdintegration_filter_specter_order_created_date |
| Force Article Update | Decide whether articles that already exist in Specter should be updated. | specter_force_article_update |
| Load stock changes from all Warehouses | Decide whether stock changes are loaded from all warehouses in Specter. | specter_stock_load_all_warehouses |
| Managed Orders statuses | Choose which order statuses an order must have in Specter to be picked up as managed or invoiced. | specter_invoiced_order_statuses |
| Map Payment methods | Connect the payment methods in Shopify with the pay types in Specter. | specter_map_payment_methods |
| Map Shipping methods (by CODE) | Connect the shipping method codes from Shopify with the external delivery methods in Specter. | specter_map_shipping_methods |
| Map Shipping methods (by NAME) | Connect the shipping method names from Shopify with the external delivery methods in Specter. | specter_map_shipping_methods_by_name |
| Map Shipping methods in Order Rows | Use different shipping fee article numbers in Specter depending on the shipping method in Shopify. | specter_map_shipment_article_no |
| Map Specter Api Keys with flows | Use separate Specter API keys for different Junipeer flows. | specter_apiuser_flow |
| Map Webshop to Pay Type System User | Use a different pay type system user for different webshops – for example different Svea merchant numbers per webshop. | map_market_pay_type_system_user |
| Map WebshopId | Give orders a specific Specter webshop ID depending on which shop or market in Shopify they come from. | specter_map_webshopid |
| Map the variant values with suffixes | Connect variant values with suffixes , so the right suffix is used when articles (variants) are exported. | suffix_map |
| Match Shipping methods by Name | Decide how the shipping method on an order is recognised. | specter_match_shipping_methods_by_name |
| Pay Type System User | Enter a pay type system user . | pay_type_system_user |
| Payment Method | Choose the pay type in the other system that should be used for this payment method. | pay_type_identifier |
| Payment Method Settings | Add specific settings depending on which payment method is used in Shopify. | specter_advanced_payments |
| Payment Reference Field | Choose which value is used as the payment reference . | reference_nr_field |
| Payout Reference Number | Choose which reference number from Shopify is used to find the matching order in Specter when payouts are sent. | specter_payout_identifier_field |
| Pricelist used for special price | Only one special price can be exported. | specter_special_price_pricelist |
| Product Numbers to ignore | List product numbers (SKUs) that should be left out when shipments are loaded from Specter. | specter_shipment_skus_to_ignore |
| Set AgentNo (Utlämningsställets Id) from this custom attribute (if not set, we use PickupLocation from shipping, set to 0 if you do not want to use it) | Choose which custom attribute on the order holds the pickup point ID (AgentNo, utlämningsställets id) sent to Specter. | specter_order_agent_no_attribute |
| Set NotifyDeliveryByMobile to 1 (set delivery notification via SMS) | Decide whether the customer should get a delivery notification by SMS . | specter_notify_delivery |
| Set PreparedShipmentId (Identifierare för en förbokad transportbokning) from this custom attribute (if not set, we use ProviderId value from shipping, set to 0 if you do not want to use it) | Choose which custom attribute on the order holds the ID of a pre-booked shipment (PreparedShipmentId) sent to Specter. | specter_order_prepared_shipment_id_attribute |
| Set stock from | Choose whether to import stock from Specter, and from which warehouse(s). | specter_import_stock_from |
| Specific WebshopIds for ViewInShop Articles | If you have several webshops in Specter, choose which webshops count when only articles marked Visa artikeln i shop (viewInShop) are exported. | specter_viewinshop_webshop_ids |
| Specter Api User ID | Enter the API user ID Junipeer uses to connect to Specter. | specter_api_user_id |
| Specter Api User Key | Enter the API user key Junipeer uses to connect to Specter. | specter_api_user_key |
| Specter PAYMENT Api User ID | Enter the API user ID for Specter payments. | specter_payment_api_user_id |
| Specter PAYMENT Api User Key | Enter the API user key for Specter payments. | specter_payment_api_user_key |
| Specter PAYMENT Sbm Id | Enter the SBM ID for Specter payments. | specter_payment_sbm_id |
| Specter PLUS Api User ID | Enter the API user ID for Specter PLUS. | specter_plus_api_user_id |
| Specter PLUS Api User Key | Enter the API user key for Specter PLUS. | specter_plus_api_user_key |
| Specter PLUS Sbm Id | Enter the SBM ID for Specter PLUS. | specter_plus_sbm_id |
| Specter Sbm Id | Enter your SBM ID from Specter. | specter_sbm_id |
| Sync ViewInShop Articles only | Decide which articles from Specter are exported. | specter_viewinshop_articles_only |
| Warehouse to import stock from | Choose the warehouse to import stock from. | specter_import_stock_from_warehouse_id |
| WebshopId for the order | If several webshops are linked to Specter, enter the webshop ID the orders come from. | specter_default_webshopid |
Settings for Dotdigital (13)
| Setting | What it controls | Key |
|---|---|---|
| Consent Attribute Fallback | Choose what happens when the customer attribute doesn't contain consent information . | dotdigital_consent_from_attribute_fallback |
| Consent Attribute Field | Enter the name of the customer attribute that holds the consent text. | dotdigital_consent_from_attribute_field |
| Consent Text | Enter the consent text that is attached to a contact when it is created or updated in Dotdigital. | dotdigital_consent_text |
| Consent URL | Enter the web address (URL) where the customer gave their consent. | dotdigital_consent_url |
| Consent from Customer Attribute | Read the consent text from a customer attribute instead of using the fixed Consent Text . | dotdigital_consent_from_attribute_enabled |
| Contact Identifier | Choose how contacts are identified in Dotdigital. | dotdigital_contact_identifier |
| Default Contact List | Choose a Dotdigital list that contacts are added to by default. | dotdigital_default_list |
| List Attribute Fallback | Choose what happens when the customer attribute doesn't contain a list ID . | dotdigital_list_from_attribute_fallback |
Show all 13 settings
| Setting | What it controls | Key |
|---|---|---|
| List Attribute Field | Enter the name of the customer attribute that holds the Dotdigital list ID(s). | dotdigital_list_from_attribute_field |
| List from Customer Attribute | Read Dotdigital list IDs from a customer attribute , instead of (or in addition to) the list settings. | dotdigital_list_from_attribute_enabled |
| Map Country to Contact List | Add contacts to a specific Dotdigital list based on their billing country . | dotdigital_list_by_country |
| Map Customer Attributes to Data Fields (Store) | Write customer attributes to Dotdigital data fields when contacts are saved. | dotdigital_map_attributes_store |
| Map Customer Fields to Data Fields (Store) | Choose which customer fields are written to Dotdigital data fields when contacts are saved. | dotdigital_map_data_fields_store |
Did this page help you?