Post by account_disabled on Dec 20, 2023 4:10:41 GMT
What will you learn in this article? we liked GDS and wanted to have our own internal data in it (economy, use of our application, etc.) so we created a connector that will be universal and will allow us to very quickly connect any data from our database but we want it all to be safe and we didn't have to make the GDSku database available, or Google so we wrote our own fast PHP API, which is configurable directly from the database creating a new data source for GDS now only involves writing an SQL query that retrieves the data and then we just draw graphs in GOOGLE DATA STUDIO and then we decided to release all the sources for you, maybe you are solving the same problem But let's go step by step.
At the beginning of the B2B Email List year, we attended a great E-shop summit & expo, where Lukáš Palkovič from eVisions finally persuaded us to put together GDS connectors for Collabim . During the processing of these connectors and several sleepless nights during debugging, we finally started to like GDS (we used POWERBI for internal reporting and we also prepared an article for you on how to very easily click on the e-shop warehouse turnover report) . So we decided to rewrite the internal reporting to GDS , but we encountered the problem that our database (from which we want to draw) is completely in AWD RDS, barricaded and cannot be accessed from anywhere (only from our internal servers).
In addition, we also don't want to let any data (especially personal) out somewhere where we don't have full control over it. Do you have any idea how much SEO revenue your website or e-shop loses every month? We will be happy to devote time to you personally. We will show you how much more money you could earn every month just thanks to SEO! And it's FREE. I want a FREE consultation >> In the end, we came up with this: we will write a universal API endpoint in Collabi, which we will be able to quickly configure through and only through MYSQL (just for speed) ideally, we just prepare the SQL query in the editor and when we are satisfied with the prepared source, we save it to the database we will write a universal connector for GDS, we will always put only the configuration and the method of our virtual API to be called and two keys for security (one identifies the user, the other is for access tQL with data preparation and then pulls the data, you is returned as JSON our PHP endpoint calls the GDS connector, which is configured with 3 parameters (method, method key, user key) well, then we already have data in GDS and can draw graphs Now you may be wondering why we have two SQL syntaxes in MYSQL.
At the beginning of the B2B Email List year, we attended a great E-shop summit & expo, where Lukáš Palkovič from eVisions finally persuaded us to put together GDS connectors for Collabim . During the processing of these connectors and several sleepless nights during debugging, we finally started to like GDS (we used POWERBI for internal reporting and we also prepared an article for you on how to very easily click on the e-shop warehouse turnover report) . So we decided to rewrite the internal reporting to GDS , but we encountered the problem that our database (from which we want to draw) is completely in AWD RDS, barricaded and cannot be accessed from anywhere (only from our internal servers).
In addition, we also don't want to let any data (especially personal) out somewhere where we don't have full control over it. Do you have any idea how much SEO revenue your website or e-shop loses every month? We will be happy to devote time to you personally. We will show you how much more money you could earn every month just thanks to SEO! And it's FREE. I want a FREE consultation >> In the end, we came up with this: we will write a universal API endpoint in Collabi, which we will be able to quickly configure through and only through MYSQL (just for speed) ideally, we just prepare the SQL query in the editor and when we are satisfied with the prepared source, we save it to the database we will write a universal connector for GDS, we will always put only the configuration and the method of our virtual API to be called and two keys for security (one identifies the user, the other is for access tQL with data preparation and then pulls the data, you is returned as JSON our PHP endpoint calls the GDS connector, which is configured with 3 parameters (method, method key, user key) well, then we already have data in GDS and can draw graphs Now you may be wondering why we have two SQL syntaxes in MYSQL.