Pre – Onboarding
1. What are the main modules in Integration?
SMS – Recurring, event triggered, broadcast, Web push – broadcast or subscription and Email- recurring, event triggered, one to one, broadcast
2.How soon can we start the integration process?
Integration process starts as soon as the authentication code is pasted on the front end of client’s website using JS. However, it also depends on the plugins that are installed on client’s website.
3. What all plugins Betaout uses?
As of now, we have Magento, Shopify, OpenCart, WooCOMMERCE.
4.What would all data we require from client’s end?
Historic data(Customer): Customer ID, Email ID, Phone, First Name, Last name, Signup date. Age and Location (for better targeting)
Historic data (Orders): Order ID, Product ID, Total Price, customer id, email id, created time, currency, discount, promo code, product selling price etcetera.
Historic data (product): Product ID, Product title, price, category, sub-category, Brand name.
5. How much time will it take to integrate a plugin?
Every plugin would take almost 30 minutes to integrate. However, once it has been done we run a quality check twice in order to ensure that in the future it doesn’t show any error.
6.On an average how much time would it take to integrate the whole system and to make it live?
Depends on the following factors: Plugin without customization: 7-10 days Plugin with customization: Depends on the customization. Custom Ecommerce Website without customization: 25-30 days. Custom Ecommerce Website with customization: 30 days. Custom Non-Ecommerce Website will definitely require customization and it will totally depend on the type of customization.
7. What would all data we be able to access?
We would have an access to the user properties, order properties which we’ve mentioned above also. Basically most of the things that the client will provide us which in any way could help us in tracking and targeting. During On-Boarding
8. What is customer ID? How do I set it? How important is it?
Customer ID is generally set up in client’s system, which is a unique ID via which a customer accesses the website, ie. Once a customer makes his account on client’s website, he will be assigned a unique ID and all his activities will be registered under this id. Generally, customer id is linked with email ID because two users might share the same name but they can’t have the same email id in any case.
This customer ID is very important because all of the details are saved within this ID. It acts as a primary key. Every user is tracked on the basis of this identical key.
9. What is an API key? What is API secret key? What is the project ID?
API key is the address of our API. API Secret Key Project ID: It is the identical key provided to you by us in order to have an access to the campaign. In layman’s language API key is the username and the project ID acts like the password in order to access the account of a campaign.
10. How do we track data?
It can be done in two ways. One: We can put up a tracker in the front end of client’s website, in either header or footer, preferably in the header, in order to track the activities of a customer. Two: We access it while forwarding the data from client’s server to our server.
11. How do we track in live data tracking?
In this case, we generally track the order ID and the customer ID, wherein we treat the order ID as our primary key and customer ID as our secondary data. In this case, we don’t switch from primary key to secondary key. Order ID has to be primary.
12. What are User properties?
User properties are generally of three types
Update: Whenever a person upgrades their attribute. For example, if a person has put a size 12 dress in their cart, but if for some reason the person changes it to size 14 then the property would be updated.
Increment: If the average amount for which a person usually buys stuff and then next time he increases it, then that increased amount would be increment.
Append: If the person usually buys a footwear of x brand and the very next time he buys footwear of y brand then, in that case, the property would be appended, meaning, whenever we will send any promotion regarding those two brands, we will pick that person in each of the cases.
13. What is the difference between Revenue and total price?
Revenue = (Product quantity*Selling Price) – Discount Amount
Total = Revenue + Taxes + Shipping Charges
14. Should a client send the email to every contact in his domain altogether?
No. It is preferable that he sends emails in packets initially, then gradually increase the number of the emails sent every day in order to maintain the quality of the domain.
15. What is SKU? How relevant is it to me?
SKU is the stock keeping unit. In some cases, owners don’t set up product ID however they do maintain an SKU. In that case, instead of taking Product ID as the primary key we keep the SKU as the primary key.
16. What do all events you create?
Purchased: Purchase helps in capturing the details of the customer purchase happened in its entire lifetime on the website.
Viewed: Viewed enables us to keep a track on the products that are usually viewed by any customer in his website lifetime.
Add to cart: Whenever any customer adds a product in his cart, the add to cart event is triggered.
Removed from cart: Similarly, whenever any customer removes a product from his cart, the removed from cart event is triggered.
Update Cart: Whenever the number of products in a cart are altered, the update cart event is triggered.
Order Placed: Whenever an order is placed and the payment isn’t done yet (COD orders), the order placed event will be triggered. However, in case of online payment, order placed and purchased is triggered almost at the same time.
Order Refunded: Whenever an order is returned, and the payment is reflected back in the user’s account, this event would be triggered.
16. If in the case of online payment, payment is incomplete or rejected or was lost midway, which event would be triggered?
In that case, only the order placed event would be triggered, purchased event would be triggered once the amount would reflect in your account. Prior to that everything would be under order placed.
We segregate SMS in two sections on the basis of their routes.
1) Transactional Route
If you would have ever noticed then some of the messages have their names such as SBISMS or OLACBS etc. These sms come through transactional route. All of these are white listed, ie. you can’t simply send any message in it. It has to be cross checked by the client. Tridoc sample is basically a contract between the messages providing server and the client. Only when the TRIDOC has been signed by both, and the content of the sms is checked, the messages are forwarded further to the customers.
2) Promotional Route
As the name suggests, all the messages sent via promotional route are promotional in nature. These messages need not to be cross checked for data as they’re generic promotional messages. They have numbers instead of alphabets in the sender’s address.
Following are the listed differences between Transactional and Promotional routes: (as listed in MSG91)
1. These can be used for
sending any type of information.
Ex. OTP, Bank Transactions etc.
1. These are specifically used for
Ex. Sale, offers etc.
2. Transactional SMS
can be sent anytime
2. Promotional SMS are sent
between 9 am to 9 pm only
3. SMS can be sent to DND numbers
3. SMS cannot be sent to DND numbers
4. In API route=4
4. In API route=1
There is one more route(SendOTP route) which is for SendOTP, if you are looking for OTP services, we would suggest you opt for sendOTP because it has various advantages over the traditional transactional route:
Voice backup for failed SMS OTPs, on our cost.
We generate the OTP on your behalf, we send and we verify. You just have to call the APIs.
The back-end algorithm makes sure that the OTP is processed from our end in less than half-a-second.
1. For how many platforms we provide plugin support ?
2. On which e-commerce platforms we provide plugin support ?
We provide plugin support for Magento, Prestashop, Woocommerce, WPecommerce, Opencart and Shopify.
3. Is there any difference in betaout JS for single page and multiple page JS script?
4.What is the difference for multiple page and single page website?
Reattach_bout is used in single page js sites and identify is used for multiple page js sites in the identify call.
5.Why it is required to send information for user agent, system info and user’s campaign info for Curl or http method but not for JS?
For JS we fetch these details real time.