vklmn

You need to validate complicated optimization ideas, it's seems to be fine extracting data from documents you already have, ask for missing info / documents and calculating numbers

I don't think that it's google's fault. Google sometimes trade ads on auctions, meaning they issue and HTTP request to partners asking "Hey, you want to show an ad here", and partner respond with price and HTML code, the highest bidder wins and HTTP code is inserted.

HTTP contains JavaScript, and theoretically anything can be executed within the browser (I've seen people mining bitcoins!).

Google can't monitor an execute every HTML snippet, but they doing pretty great job sampling responses and evaluating some of them. Fraudsters are smart, and trying to understand if the code is executed on Google's servers, but overall they are loosing.

It seems like a case where google's system didn't work.

By they way, all google partners are listed here: https://developers.google.com/third-party-ads/adx-vendors. Usually, it's possible to track down who's exactly responsible by looking at dev console

Hi! We don't have plans to add Vertica yet. But if your team is willing to help or send PR we can reconsider!Feel free to reach out directly to me at [email protected]

Yes, just add more jitsu nodes. It's hard to answer how many nodes do you need (depends on transformations, CPU/RAM/etc), but you can count on thousands request per second per node at least

Thanks, we will fix that!

That's what the website missing indeed. We have a few words about that in docs, but it's still not enough https://jitsu.com/docs/internals/jitsu-server#mapping-step

Overall, Jitsu tries to decompose (aka flatten) JSON as deep as possible. E.g. {a: {b:1, c:2}} will become a_b=1, a_c=2. If column is missing, it will be created. We don't decompose arrays so far

Two reasons a) you can push events from your apps b) if you want to have more connectors available (Singer, and few native connectors)

Check the answer in another thread! https://news.ycombinator.com/item?id=29106531

Thanks for observation! We will add it. A fresh look to marketing materials is always appreciated!

Mixpanel will store the data for you and do visualization. Jitsu just help you to get you data to your data warehouse.

Downside: you'll need to build all visualization by yourself. Fortunately that's easy with tools such as Looker, Mode, Metabase etc

Upside: you can do with your data whatever you want - built any reports, join with other datasets etc. You not limited by reports MixPanel team build.

In reality, Jitsu and MixPanel could co-exist. Jitsu support s MixPanel as a destination (e.g. you send data to Jitsu ; Jitsu sends it to MixPanel and data warehouse).

You can hack almost anything using inbound Event API (https://jitsu.com/docs/sending-data/api) and JavaScript transformations (https://jitsu.com/blog/javascript-transform)

Yes, if segment compatibility mode is enabled

Thank you!

1. Thats exactly the reason we have native connectors for Facebook and Google Ads (we didn't use ones from Airbyte and Singer). Jitsu can pull any combination from FB/GAds — it's almost like SQL! Airbyte/Singer just can't do that. Later we're going to vet other connectors too and decide if we need to re-implement them

2. We have functions too! https://jitsu.com/blog/javascript-transform

The same way as Kafka. Jitsu nodes (=collection agents) writes to write ahead log, and then either sends data to destination right away, or sends data in batches.

That's a chance you have to take when you're making this decision!

We have some overlap. In simple words: a Singer + DBT, Jitsu is Event Collector + Singer + Airbyte.

Meltano will pull data from Singer connectors and do transformations, but they won't run Airbyte connectors, and you can't push data to Meltano

Jitsu will use Airbyte or Singer to pull data, and you can push the data to Jitsu. But Jitsu won't run DBT transformation. Although we can trigger DBT cloud jobs: https://jitsu.com/blog/dbt-integration

P.S. Meltano has a CLI, and we don't (yet)

There's always a tradeoff. By describing our company as "alternative to X" you saving tons of time by explaining what you company does. People are overloaded with information, and average attention span very short. But I see the disadvantages too! We have an internal debate about tagline a few months ago, and essentially decided to go with "Open-source alternative to Segment". But it wasn't an easy decision!

However, I think that the product matters the most. You can change the tagline in a few clicks. Can't say the same about the product

We have suggested event structure (https://github.com/jitsucom/jitsu/blob/master/javascript-sdk...). If you want to send data to destination, you should either follow suggested structure or write your own JavaScript mapping (https://jitsu.com/blog/javascript-transform).

And we have DBT models too https://hub.getdbt.com/jitsucom/jitsu/latest/ !

We call it "push" (you send event to Jitsu) and "pull" (Jitsu pulls data) integrations. Technically speaking, push integrations are outnumbered. But that's because we took advantage of other open-source projects (Airbyte and Singer) to implement them.

Our core is push integrations, that's the most complex part of the system. We see "pull" integrations as an additional feature that helps to enrich the data after events made it to DHW

To be honest, we just grab a first short .com domain name we liked a) which was available at reasonable price b) we like

Essentially we're doing same thing. But we build Jitsu to be as simple as possible: you don't need to setup multiple services (just one Docker service!), data goes to DWH almost instantly. And we can pull data from more that 100 external APIs

Think of us as Snowplow 2.0 )

Jitsu certainly can be used to build spyware (and Linux too, probably 90% of spyware is running on Linux servers), but following this logic any OSS project can be accused of being spyware. I

Yes, jitsu can be deployed at custom domain such as track.yourcompany.com. And while some AdBlockers will block *.segment.com, track.yourcompany.com will remain functional. We don't consider this feature unethical, though. It depends on how data collected by Jitsu is used. If the app owner sells it without telling end-users that's probably bad. However, I believe most of our users using the data to improve product experience. And Jitsu can be configured to respect do-not-track/gdpr settings.

Jitsu can multiplex events and send it to different destinations too. I admit, we don't have that much destinations as Segment (we support Amplitude, Hubspot, GA and Facebook). But we can send data to any HTTP-enpoint (see Webhook destination). Since the body of HTTP request is a JavaScript expression, with a little hacking you can support almost any service.

You mean we don't have libs for Mobile platforms / backend frameworks? That's true, tough we have iOS SDK[1] and community maintained Go client. However, all libs are merely wrapper around http api[2]. We will implement other client libs soon, but calling HTTP API directly works very well too

[1] https://jitsu.com/docs/sending-data/mobile-apps/ios-sdk [2] https://jitsu.com/docs/sending-data/api

Ops... Thank you very much! Vercel is deploying the fix already

We're very similar indeed. But we attack the same problem from different angles:

- We truly believe that our product should be accessible for small teams too. That's why se made Jitsu very easy to deploy. I'm not sure you can deploy Rudder on Heroku, or on any service with a single Docker file.

- Our ETL component is open-source (and based on other great OSS projects - Airbyte & Singer). RudderStack haven't published the Cloud Extract (their ETL) to my knowledge.

- RudderStack aims to replace Segment, we go beyond that. We didn't copy Segment API one-to-one, we just added a Segment compatibility layer. Jitsu can be used for any kind of data. An example: a few companies (including our-selves) using Jitsu to collect open-source telemetry (anonymous usage). I'm not sure Rudder can be used for that use-case